3 ms·

Would you care elaborating why it is better than HTML5?

• kevingadd 7y ago
  "HTML5" + things like css grid and flexbox that you need to build UI in a sensible manner are pretty new inventions. XUL predates them dramatically, building UI in HTML at the time would have been an absolute nightmare. I know because I had to ship it in multiple applications
  • The_rationalist 7y ago
    I understand that it probably was a better technology at the time. But are there any concepts/technologies in XUL that would be useful to add in the HTML standard?
    • xeeeeeeeeeeenu 7y ago
      It's a minor problem, but CSS, unlike XUL, doesn't provide a way to crop text in the middle[1][2]. [1] - https://www.w3.org/wiki/Text-overflow_middle_cropping https://www.w3.org/wiki/Text-overflow_middle_cropping [2] - https://developer.mozilla.org/en-US/docs/Archive/Mozilla/XUL/Attribute/crop https://developer.mozilla.org/en-US/docs/Archive/Mozilla/XUL...
      • roca 7y ago
        Cropping text in the middle is extremely hard to spec and implement for general inline CSS. Cropping at the start or end can be implemented as a purely paint-time operation. Cropping in the middle means you have to change the layout, and you have to define the layout of the stuff in the middle that has been cropped away in case someone does element.getClientRects() etc. It is far from obvious how that should work. XUL texboxes avoided this problem by only supporting a single plain text string, but applying that constraint to HTML+CSS would be incredibly ugly (and people soon be complaining about that constraint, anyway).
• loeg 7y ago
  HTML5 (2014) and Firefox 1.5 (2005) were not contemporaneous.
• vbezhenar 7y ago
  I think that XUL had better layout engines, suitable for apps instead of web pages. May be with modern CSS this gap is closed. Also native controls were nice.