Live data from Hacker News

Firefox.html: Rebuilding Firefox UI in HTML

mail.mozilla.org

41–50 of 146 posts

Re: Firefox.html: Rebuilding Firefox UI in HTML

#41
Interesting. But on Android Mozilla already deviated form this approach of "webbiness" in favor of using native UI. Same as Sailfish browser does with Qt and Gecko through IPCembedlite.

If not for that, Sailfish browser could reuse the UI.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#42

I realize this is a personal project, but this is deeply amusing considering that: 1. Way back when (circa 1998-2001?), the Mozilla project started as a radical redesign of the next gen Netscape browser. One of the core principles of the architecture was that the browser itself would render the UI elements (using an HTML-like tech call XUL). 2. The Firefox browser (then called "Phoenix") was a reaction against the ab…

> Originally Phoenix was the Gecko engine in a native UI window without all the XUL overhead

I'm not sure Phoenix was ever a reaction to XUL. Phoenix was more a reaction to the kitchen sink feature-list of Netscape 5 and Mozilla Application Suite, seeking to pare down the feature set to a minimally viable browser.

In XUL (and moreso XBL) Mozilla had a web technology that there was talk of submitting for standardization and which brought with it a level of expression that HTML didn't offer at the time. As HTML, CSS and JavaScript have evolved, XUL/XBL bring less and less to the table.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#43

I've built that. Just to be clear: this is a personal project, not a mozilla project (even though I'm a mozilla employee). Also - many people find it silly to use HTML instead of the operating system toolkit library. But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). For example, if you run…

> But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget).

No troll, I thought that was what XUL was.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#44

Earlier quoted context omitted.

Why don’t you use SVG instead of PNG for icons? Then you can use CSS to customize them for different themes.

I want to use SVG. See issue #24. I just don't have the assets.

It might even make more sense to just use fonts for the icons and leave SVG out of it entirely. I'm referring to the OpenType COLR/CPAL tables Microsoft is pushing:

http://opentype.info/blog/2013/07/03/color-emoji-in-windows-...

Re: Firefox.html: Rebuilding Firefox UI in HTML

#46

I've built that. Just to be clear: this is a personal project, not a mozilla project (even though I'm a mozilla employee). Also - many people find it silly to use HTML instead of the operating system toolkit library. But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). For example, if you run…

> But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). No troll, I thought that was what XUL was.

Problem being that XUL is quite long in the tooth?

There might be other advantages of replacing XUL with HTML, rather than developing them in parallel.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#47

I've built that. Just to be clear: this is a personal project, not a mozilla project (even though I'm a mozilla employee). Also - many people find it silly to use HTML instead of the operating system toolkit library. But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). For example, if you run…

Between that, rust and servo, it seems we have a new experimental technology stack shaping for the future of firefox.

It may or may not be used in the end, but I'm excited by the potential.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#48

Earlier quoted context omitted.

> But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). No troll, I thought that was what XUL was.

Problem being that XUL is quite long in the tooth? There might be other advantages of replacing XUL with HTML, rather than developing them in parallel.

The problem (or at least one of them) is that maintaining XUL and HTML is expensive. XUL, like HTML, has a bunch of weird corner cases, tricky layout behavior, complex interaction between elements, etc. The focus of the platform developers at Mozilla is obviously on the Web, so XUL has been in a crappy maintenance mode for a long time now.

Doing the Firefox chrome (heh) in HTML is another way to put our money where our mouth is, like the Firefox OS and Web App Runtime efforts.

There's a more detailed explanation of the situation of XUL here: https://lists.mozilla.org/pipermail/dev-platform/2014-Octobe...

Re: Firefox.html: Rebuilding Firefox UI in HTML

#49
post #2

The browser shipped with Blackberry 10 was written in HTML and was a real joy to develop. Edit: some more public details The default browser on the BlackBerry 10 platform was a completely new browser application. The chrome was written in HTML, CSS and JavaScript. Being able to develop the chrome on your desktop browser or being able to run inspector remotely and using your desktop was very handy. The core was a comm…

Another very cool feature I forgot about was that when developing the browser application on the device it would not actually have any browser bits on the device, but just have the environment variable CHROME_URL set to my desktop where I had a webserver serving up my browser files. This let me very rapidly develop the html/css/javascript code without having to transfer my "mobile app" to the device. Reducing the edit/"compile"/see cycle was a big win.
Post reply on HN