Re:MDN Redesign
by mjw1007 on Tuesday March 01, 2022 @01:40PM
(#30518107)
The explanation in the article is: « So you don’t have to keep version numbers in your head, we’ve put more emphasis on yes and no iconography for browser capabilities »
But as far as I can tell all they've done is put a tick there if any version of the browser supports the feature.
That means I could have learned the same information from the old table just by looking at whether the cell had anything in it, with no version numbers "in my head" at all. So I'm feeling patronised rather than helped.
If they'd done a bit more work and made the ticks indicate something like "available in the oldest supported version of the browser" (which is a recent version for Firefox and Chrome but not for Safari), that might have justified what they wrote.
Re:MDN Redesign
by sings on Tuesday March 01, 2022 @06:29PM
(#30521496)
It’s a bit surprising that the linked article isn’t more carefully written to explain choices, given the audience. As you say, the reason given doesn’t hold up to any scrutiny.
But as far as I can tell all they've done is put a tick there if any version of the browser supports the feature.
That means I could have learned the same information from the old table just by looking at whether the cell had anything in it, with no version numbers "in my head" at all. So I'm feeling patronised rather than helped.
If they'd done a bit more work and made the ticks indicate something like "available in the oldest supported version of the browser" (which is a recent version for Firefox and Chrome but not for Safari), that might have justified what they wrote.