| Deutsch English Français Italiano |
|
<c53a1a205c.DaveMeUK@BeagleBoard-xM> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: David Higton <dave@davehigton.me.uk>
Newsgroups: comp.mobile.android
Subject: Re: Slashdot on Samsung browser
Date: Tue, 20 May 2025 19:50:11 +0100
Organization: Home
Lines: 30
Message-ID: <c53a1a205c.DaveMeUK@BeagleBoard-xM>
References: <4a710f205c.DaveMeUK@BeagleBoard-xM> <100ind2.knc.1@ID-201911.user.individual.net>
Injection-Date: Tue, 20 May 2025 20:50:22 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="a4ae0c703c02c4abf6d767464ee274ac";
logging-data="2509112"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+1OqDtebzwpCoyw8t6UWhSNh4VhVZvOTQ="
User-Agent: Messenger-Pro/8.03 (MsgServe/8.01) (RISC-OS/5.31) NewsHound/v1.55
Cancel-Lock: sha1:s5PN3FQz/ZAIvda3/NCplQGkXMk=
Bytes: 2195
In message <100ind2.knc.1@ID-201911.user.individual.net>
Frank Slootweg <this@ddress.is.invalid> wrote:
>David Higton <dave@davehigton.me.uk> wrote:
>> Can some of you with access to a Samsung browser please try
>> https://slashdot.org on a Samsung browser and some other browsers?
>>
>> I use a Samsung S24 and a Galaxy Tab. Until a few weeks ago, the
>> Samsung browsers used to render Slashdot like other browsers do.
>> Something changed; I don't know whether it's a Samsung browser update
>> or a site update, but it looks radically differnet now - and rather
>> harder to read, with tiny text. Pinch to zoom allows the text to be
>> magnified, of course, but then the page has to be scrolled sideways
>> to read entire lines of text.
>>
>> I'd just like to know why it is like it is. A solution would be
>> even better!
>
> Looks fine to me, both in (Samsung) 'Internet' and (Google) Chrome.
>
> Note however that <https://slashdot.org> is redirected to the mobile
>site <https://m.slashdot.org>.
Aha - that's it, thank you, Frank. For some reason my devices had
switched over to the mobile site. Once they're back to non-mobile,
I can read the site on my mobiles.
Something's fundamentally wrong there, isn't it?
David