81–90 of 131 posts
Aside: This article is a decent usecase for the esoteric `image-rendering: pixelated;` css property.
I used it to make this PWA work well on iPhones: http://dmitry.gr/89
I was able to zoom out and see everything, but some people don't know (or wouldn't think of) that trick.
Earlier quoted context omitted.
HEAD support is never a guarantee, and content type auto detection is just another kind of heuristics.
Ugh, HEAD is not being universally supported, at least for static content? Okay, I accept that this has value then. As for the MIME type, for image types I'd say it's more than stable enough. Certainly much, much more stable than the 6.7% error rate mentioned in the article here, I'd be surprised if it was even 1%. If you double click on an image on your desktop for example, you can in almost all cases expect that it…
They’re not used for rendering, they’re used for figuring out what to fetch. A HEAD request would be far less efficient than knowing ahead of time what to fetch: 1 request versus 2N+1 requests.
What you suggest sounds all fine but the entire web is user input for a browser, so no matter what, you need to define how to fail. If you can fail gracefully, you might as well do so, because a failure might not even be triggered by bad code/configuration on your side but simply by flaky network issues.
I suspect an animation. Anybody know how to find out?
Earlier quoted context omitted.
Ugh, HEAD is not being universally supported, at least for static content? Okay, I accept that this has value then. As for the MIME type, for image types I'd say it's more than stable enough. Certainly much, much more stable than the 6.7% error rate mentioned in the article here, I'd be surprised if it was even 1%. If you double click on an image on your desktop for example, you can in almost all cases expect that it…
You might be overthinking this. I agree with the philosophy that stricter is better, but in this case what do you expect broken hints to do? They’re not used for rendering, they’re used for figuring out what to fetch. A HEAD request would be far less efficient than knowing ahead of time what to fetch: 1 request versus 2N+1 requests. What you suggest sounds all fine but the entire web is user input for a browser, so n…
I do wish that content negotiation (e.g. Accept headers) worked properly. In the end though, those hints implement a subset of content negotiation in a reasonable way, given the state of affairs.
Earlier quoted context omitted.
I used it to make this PWA work well on iPhones: http://dmitry.gr/89
I loaded this up on a surface tablet--it renders larger than my viewport, but with no scrollbar. I was able to zoom out and see everything, but some people don't know (or wouldn't think of) that trick.
I worked on Opera Link, the first built-in synchronization between different installations of the Opera browser, both desktop, Opera Mini and Opera Mobile (+ a web view). Favicons got included in the data from day one, and it was awesome to get the look and feel of your bookmark bar/UI with the correct icons right away. Back then we stored the booksmarks in a home grown XML data store (built on top of mysql, acting m…
> I recommend that browsers ignore these hints because they are wrong much of the time. We calculated a 6.7% error rate for these attributes, where the size is not found in the image or the type does not match the file format.
I think of much in this context to mean at least more than 50% of the time. So I had to look up the definition of the word. One definition from Merriam is "more than is expected or acceptable : more than enough." So I guess the usage is acceptable!
I always enjoy finding I have a slightly wrong definition in my mind for a word. Many arguments, or much arguments, fail to move forward due to the differing, unidentified, underlying assumptions relying on words with slightly different definitions, both people having a slightly different question they are arguing in their mind.
It's interesting to ponder how many hundreds of bytes are exchanged between the browser and the site just for a simple GET request for the image.