Mozilla once again notices that, in spite of the lavish salaries they heap upon their techbro executives, Firefox’s userbase continues to dwindle. Could this be because they don’t operate a monolithic surveillance advertising racket? Or maybe it’s because the corners in the UI aren’t round enough.
https://www.firefox.com/en-US/whatsnew/157/
Choice quote from that interview, which was important enough to get a big box in the release notes too:
We are bringing back compact mode as well
We removed it for absolutely no goddamn fucking reason, despite numerous objections, and now we’re bringing it back! This is called ‘listening’, you see. We are very dependable can definitely be relied upon to provide a stable browser that you won’t have to worry about.
Somehow those executives just can’t work out that unless you can advertise Firefox in all of the search engines and youtubes and gmails and docs and drives and whatever the fuck and preinstall it on all the phones, the Chrome users will not come. “Ooh shiny” is the least of anyone’s concerns.
no, it’s very much not up to web standards yet. it has a super fast html renderer and css engine that support something like 70% of properties, a very barebones js runtime that has basically no browser apis, and a frontend that (i think) only takes urls via command-line.
When was the last time you looked into servo because this is dated at best, bordering on misleading. The js support has increased massively over the past year with things like intersectionobserver, shadow dom, and dozens more apis. Stylo supports many newer and advanced css features, of note recently is grid support. And the frontend servoshell has taken urls for a rather long time. If you try it out today with experimental features enabled you’ll find that most websites mostly work.
last year, admittedly. good to hear that it’s coming along!
The less APIs the better, some of the information my phone is giving out currently to evwry site I visit is ridiculous
some of them are, y’know, needed for the sites to do anything at all.
I know I am only joking, lynx ftw
Honestly that description kinda makes me want to target servo for all of my hobby browser-backed UIs. Html5 with forms can do a surprising amount (albeit not always as effortlessly as just including a JavaScript library) - though I expect something like IndexedDB isn’t at all available?
EDIT: well, the servo repo has a bunch of code in a
storage/engines/indexeddbfolder, but the repo aussi has about 30 open issues relating to “IndexedDB” in one way or another.I’m currently targetting CSS 2.0 for one of my projects. I’m trying to make it work right on a 3DS, Netscape Navigator, IE and, of course, Servo, without serving custom files to each other.
It’s been incredibly annoying, but also fun to learn about standards from 1998, and how browsers handled them.
It’s also disheartening to learn that the modern web is, at its core, designed not to run on basically anything older than 2016.
i don’t know if they’re going in version order with implementations either so that’s an extra complication