I'm not talking about canvas in the current article - simply a HTML img tag. If you think something I wrote about was incorrect, please do get in touch with what it was and perhaps point me towards a resource that has the correct information as I am always looking to improve my knowledge and get better at what I do and it would be greatly appreciated.
What's with all these articles where the title says something but then TFA says the total opposite, and yet the article gets a ton of upvotes and no comments?
The author here goes on to say that they don't believe there is any difference in the decoding logic.
I'm not sure this is a truly misleading article. And it's interesting enough to warrant upvotes.
I will say that when I read the title, I thought "hey, this is going to be some PNG that displays a penguin in Chrome and an orange on Safari". But it's actually about an API method called "decode" and how to use it to display an image with a flicker or something.
I don't think the author misled anyone, but rather your own mind is guilty of that.
'Now I don't think Chrome has implemented this feature in any other way from Firefox, except that for some unbeknownst reason it is a lot slower, but I do think that the two browsers decode images in a different way.'
It's a result of conflating the decoding itself, which is identical, with how images are swapped in or out.
There’s is nothing about how browsers decode images here. This is an article about an event called “decode” which you can await. It would be more interesting it was titled this way.
We can change the title if someone suggests a better one. That means: accurate, neutral, and preferably using representative language from the article itself.
13 comments
[ 2.9 ms ] story [ 47.9 ms ] threadIf you paint an image on canvas when it’s not ready, the browser won’t wait for it, the frame will be blank and skipped.
The author here goes on to say that they don't believe there is any difference in the decoding logic.
I will say that when I read the title, I thought "hey, this is going to be some PNG that displays a penguin in Chrome and an orange on Safari". But it's actually about an API method called "decode" and how to use it to display an image with a flicker or something.
I don't think the author misled anyone, but rather your own mind is guilty of that.
'Now I don't think Chrome has implemented this feature in any other way from Firefox, except that for some unbeknownst reason it is a lot slower, but I do think that the two browsers decode images in a different way.'
It's a result of conflating the decoding itself, which is identical, with how images are swapped in or out.