Remember when a tab freezing didn't make Firefox's UI chrome unresponsive? I do, too.
I remember when it did — before the "Electrolysis" project, when everything ran in one process. This was quite a long time ago already.
The Firefox UI Is Now Built with Web Components
41–50 of 260 posts
Re: The Firefox UI Is Now Built with Web Components
#42Earlier quoted context omitted.
Because the API is really ugly. I can't see them ever taking off except maybe as an implementation of another library with a cleaner API.
This is one of the goals of Polymer- a cleaner API/abstraction layer on top of web components, right?
So we finally got a goddamn proper standard and we're already cheering for the next API to throw in front of it to make it "cleaner"?
Re: The Firefox UI Is Now Built with Web Components
#43Earlier quoted context omitted.
Firefox used to be built in a custom markup language called XUL, which had a number of security issues over the years as it got less attention than the HTML, etc used to render page contents. So this should help Firefox be more secure, by decreasing attack surface.
But XUL was simpler, wasn't it?
The article talks about XBL (the binding part of XUL?):
> There are hard to debug complications with binding lifecycles in our UI, and very few people know how it works.
> It adds enormous complexity to our platform in the frame constructor, style system, and the DOM implementation.
Re: The Firefox UI Is Now Built with Web Components
#44'There was also a case where a user with over 1500 tabs open (scientifically considered a “tab hoarder”)' - by what metric?
Re: The Firefox UI Is Now Built with Web Components
#45Poor web components. Everybody rags on them.
It’s one of those things where you’re only going to notice it as a user when it’s broken.
Re: The Firefox UI Is Now Built with Web Components
#46'There was also a case where a user with over 1500 tabs open (scientifically considered a “tab hoarder”)' - by what metric?
That's the joke.
Re: The Firefox UI Is Now Built with Web Components
#47This is awesome!
Re: The Firefox UI Is Now Built with Web Components
#48Earlier quoted context omitted.
This is one of the goals of Polymer- a cleaner API/abstraction layer on top of web components, right?
So we finally got a goddamn proper standard and we're already cheering for the next API to throw in front of it to make it "cleaner"?
Actually, no. There's no need or possibility to make it "cleaner", but there's always the direction of making it more "high level". These are very different things.
If you look at https://lit-element.polymer-project.org — it's just a base class that integrates declarative DOM templates.
The platform APIs are not opinionated about templating, they just provide proper mechanisms for declaring elements and having isolated DOM subtrees. It makes sense to leave templating to libraries, because… well, good luck on getting even just two people to agree about how templating should be done :)
Re: The Firefox UI Is Now Built with Web Components
#49can it cause perfomance issue ? I know for example the devtool is written in react and it's a lot slower than chrome devtools (I don't know how chrome devtool is written) and the javascript debugger is sometime not even usable because it's so slow.
I believe the developer consoles for all three major desktop browsers (Chrome, Firefox, and Safari) are written using web technologies.
Yes. In fact, "Safari devtools" are really a part of upstream WebKit. You get them in e.g. Epiphany (GNOME Web) too.
Re: The Firefox UI Is Now Built with Web Components
#50Earlier quoted context omitted.
I believe the developer consoles for all three major desktop browsers (Chrome, Firefox, and Safari) are written using web technologies.
Yes. In fact, "Safari devtools" are really a part of upstream WebKit. You get them in e.g. Epiphany (GNOME Web) too.
Yup, I'm aware and use the on GNOME Web too. It's fun to point the web inspector at itself :)