4 ms·

Not so fast, in areas where the bug can be phrased as basic compatibility with a recognized standard it is often easier to get Google (or Apple, or ..) to flinc

by yakak 5y ago

Not so fast, in areas where the bug can be phrased as basic compatibility with a recognized standard it is often easier to get Google (or Apple, or ..) to flinch than areas with a mixed standard/implementation they think they own.

Abishek_Muthian 5y ago
> Not so fast, in areas where the bug can be phrased as basic compatibility with a recognized standard it is often easier to get Google (or Apple, or ..) to flinch Unfortunately, Like the parent I've been following couple of bugs for years which Google didn't 'flinch' yet; 'Chromium on Linux not respecting prefers-color-scheme when dark GTK theme is set'[1] is one such bug. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=998903#c83 https://bugs.chromium.org/p/chromium/issues/detail?id=998903...
- yakak 5y ago
  It looks to me like they tried to flinch or at least didn't close it like almost everything UX I've seen on the chromium bug site. Pretty impressive given that while gnome is external its not an actual standard of the sort the Posix or RFC networking gangs kick each other in the crotch over. If they aren't publishing formal standards to an outside body that starts picking up independent interested parties, I think they will have more options to go down from their current quality whether or not the current quality is acceptable to critics today.