271–280 of 333 posts
> awesome free roaming 2G So instead of fixing the real problem - which is obviously connectivity - we need to break the web and add another layer of Javascript complexity to something that works perfectly fine without. It's 2016. 2G is 25 years old (started in 1991!). Stop being cheap. Stop working with 2G.
Earlier quoted context omitted.
Heck, this is my #1 complaint of almost anything on a mobile browser. It's easily the worst offender when it comes to mobile in general; I wish browser vendors put a bigger focus on fixing this, somehow.
Google is fixing it, but it's punishing them in search, not Chrome. http://arstechnica.com/business/2016/08/google-to-punish-sit...
Earlier quoted context omitted.
Browser vendors against adclicks, mice against cheese, bees against honey, what you gonna do now?
Mice aren't really interested in cheese.
Earlier quoted context omitted.
As much as I believe font matters, I really think people should just use system fonts in general. No content is definitely more annoying than ugly content, but I have a seething hatred for webpages who jump around as content loads. "Let's click on this link... ah, not that link, let's go back. Yes, this link... NO! STOP MOVING!" Besides, I'm used to my fonts. I know your fonts are a deliberate design choice, but I'm…
Using system fonts becomes a minefield once you realise they tend to be unique to each platform.
Telepathic sensitivity to designer intent is extremely common! Don't let elastic, robust CSS layout techniques mess with your pixel-perfect templates!
I absolutely do not understand the need for 'web fonts'. Just specify a normal font that most users already have installed in CSS, with some fallbacks. 'Progressive styling' is way more annoying (in my humble opinion) than waiting some time. Pages like the verge can take minutes anyway, when the wifi is not optimal. When you do things progressively, the page just keeps on changing, and the page can't really be used.…
The shifting page layout is a symptom of a broader problem, in that it's impossible to accurately predict or specify the rendered dimensions of text. Even measuring a container after the fact is unreliable because of the arbitrary amount of whitespace in different fonts. You'd have to generate a bitmap image and detect a bounding box around the pixels, which definitely won't help with loading times. This can't be don…
Are the proprietors of these sites, which live and die on their traffic, actually unaware of how bad the experience is?
Or are the proprietors oblivious because they always have the latest iPhone or Galaxy? Are the developers oblivious too, or are they keeping their bosses in the dark?
Or are the business requirements for the sight so absolutely needed, and it is simply hard to make it work?
Anyone able to venture a perspective on this?
Earlier quoted context omitted.
Why aren't you using Reddit Sync yet? Who uses the mobile site these days anyway?
For me it's about tabs. Can't stand when an app opens a URL in a mini browser inside itself. If it's a web link just open it in the damn browser!
Btw, opening the website in the Chrome tab is basically the same (session state, cookies are same) as opening it in Chrome, it's just way faster - specially on RAM challenged devices.
Earlier quoted context omitted.
It was 80 columns to match a punch card, AIUI, not a decision on readability grounds at all.
And why was a punch card 80 columns?
Earlier quoted context omitted.
The shifting page layout is a symptom of a broader problem, in that it's impossible to accurately predict or specify the rendered dimensions of text. Even measuring a container after the fact is unreliable because of the arbitrary amount of whitespace in different fonts. You'd have to generate a bitmap image and detect a bounding box around the pixels, which definitely won't help with loading times. This can't be don…
Seems like it could at least be mitigated on the browser's side though: "This text was at the top of the viewport before the restyling, so let's scroll the document to the point where that text still appears at the top."