4 ms·

Sure, they tick off more of the feature list, but it is buggy! Often there is no way of getting around the bug other than doing browser detection and turning of

Sure, they tick off more of the feature list, but it is buggy! Often there is no way of getting around the bug other than doing browser detection and turning off that feature for Safari! Two examples come to my mind: Indexeddb and suddenly changing the behaviour of taps on homescreen apps but NOT in Safari. It is one thing not having support for a feature, and it is another shipping a broken implementation. Also, there is ZERO communication on if/when a bug will be fixed.

Tloewald 11y ago
Wake me up when Chrome or Firefox have decent accessibility and then explain to me why I should care about indexeddb support over battery life or accessibility. IE only ever had decent accessibility support because it was ubiquitous and third-parties provided a solution.
- marcosdumay 11y ago
  You know, I'm getting quite tired of the accessibility argument. On this specific cases, I do know that browsers have problems (including Safari, mind you), but people just throw the word "accessibility" around as if it was a specific concept, instead of the actually actionable option of complaining about specific problems. (Who is it that can not access Chrome and Firefox? Is it blind people? People with bad eyesight? People with bad motor skills? Paralytic people?) That has the effect of making your comment just vague enough to be impossible to argue with (however true it is), but still appear specific enough to make people think it has a meaning. Besides, yes, we should make the world accessible to impaired people. But we also should not make the other 80% of the people hostage of the first group. For some reason, accessibility arguments are almost always claiming that everybody must use the worst alternative because some undefined subgroup of those 20% can't use the better one.

4 ms·

Sure, they tick off more of the feature list, but it is buggy! Often there is no way of getting around the bug other than doing browser detection and turning of

by zawaideh 11y ago

Tloewald 11y ago
Wake me up when Chrome or Firefox have decent accessibility and then explain to me why I should care about indexeddb support over battery life or accessibility. IE only ever had decent accessibility support because it was ubiquitous and third-parties provided a solution.
- marcosdumay 11y ago
  You know, I'm getting quite tired of the accessibility argument. On this specific cases, I do know that browsers have problems (including Safari, mind you), but people just throw the word "accessibility" around as if it was a specific concept, instead of the actually actionable option of complaining about specific problems. (Who is it that can not access Chrome and Firefox? Is it blind people? People with bad eyesight? People with bad motor skills? Paralytic people?) That has the effect of making your comment just vague enough to be impossible to argue with (however true it is), but still appear specific enough to make people think it has a meaning. Besides, yes, we should make the world accessible to impaired people. But we also should not make the other 80% of the people hostage of the first group. For some reason, accessibility arguments are almost always claiming that everybody must use the worst alternative because some undefined subgroup of those 20% can't use the better one.