Bugs I’ve filed on browsers | Read the Tea Leaves
I think filing bugs on browsers is one of the most useful things a web developer can do.
Agreed!
A good overview of the unfair playing field of web browsers, dominated by the monopolistic practices by Google and Apple.
Mozilla is no longer fighting for market share of its browser: it is fighting for the future of the web.
I think filing bugs on browsers is one of the most useful things a web developer can do.
Agreed!
What I want instead is an anarchist web browser.
What I’d really like to see is a browser that cuts things out, that takes things away from the web. Colors, fonts, confusion. Do you need an enormous JavaScript engine under the hood to power a modern web browser? I don’t think you do. Do you need all the extensions? All the latest CSS features? Nah, mate.
Throw away everything and start again and focus intensely about what people care about when it comes to the web.
A browser extension that will highlight the actual search results on a Google search results page—as opposed to Google’s own crap. Handy!
Or you can use Duck Duck Go.
This is a great bit of detective work by Amber! It’s the puzzling case of The Browser Dev Tools and the Missing Computed Values from Custom Properties.
Who do I know working on dev tools for Chrome, Firefox, or Safari that can help Amber find an answer to this mystery?
Like Brad, I switched to Firefox for web browsing and Duck Duck Go for searching quite a while back. I highly recommend it.
The best lack all conviction, while the worst are full of passionate intensity.
Why do browsers that don’t implement stylesheet switching still download alternative stylesheets?
Jake’s got an idea for improving the security of displaying URLs in browsers.
Opening an external link in a web view appears to trigger a reload of the parent page without credentials.
Comparing browsers.