3 ms·
Extensions (besides their other issues such as security) are also chrome-specific and require chrome-specific knowledge to write. CSS stylesheets are nicely po
by snogglethorpe 13y ago
Extensions (besides their other issues such as security) are also chrome-specific and require chrome-specific knowledge to write.
CSS stylesheets are nicely portable and should work in any (well, most) browser.
In general, a browser agnostic solution is preferable to a browser-specific solution, if they have the same functionality....
Stylesheets are also arguably much simpler to write, and far more concise for their problem space.
Maybe if user stylesheets didn't exist, you could say it isn't worth the effort to implement them, as javascript extensions are a "good enough" solution for a somewhat rare circumstance. But actually removing the existing, standardized, portable, feature seems a tad bizarre... [It's hard to believe it required much code.]
- 8ig8 13y ago> In general, a browser agnostic solution is preferable to a browser-specific solution, if they have the same functionality.... This is a great point. If a user went through the trouble of creating custom styles to make certain sites accessible, browsers should follow a standardized way of managing these styles. Just like a user can import their bookmarks when changing browsers, styles should be handled similarly. It might be extra effort for browsers to handle this uncommon feature, but it is the right thing to do, especially for users facing accessibility issues.