3 ms·

I'm not sure what you are trying to say, but the parent comment said > they recently announced that the UI is web component based - which means that using Serv

I'm not sure what you are trying to say, but the parent comment said > they recently announced that the UI is web component based - which means that using Servo for the window chrome is in the realm of possibility IMO some of the key words there are "web component" and "Servo": 1. IIRC you can't render XUL strictly with web components or anything that would be called "web", since that usually refers to web standards or something you would use from a webpage but not included as a standard (non-standardized extensions, flash, silverlight and so on). 2. Regarding the Servo part, I don't think that Servo ever included XUL support at all. Servo isn't used wholesale as the rendering engine in firefox, but the parent comment talks about the possibility to use it and web standards for the browser chrome. I feel like you are responding to a comment that never was and then responding to a comment on that comment by saying the original comment was something you thought it was, but it wasn't.

cxr 7y ago
Funny, I feel the exact same way. > IIRC you can't render XUL strictly with web components or anything that would be called "web" > use [Servo] and web standards for the browser chrome. Geez, this is excruciating. If you want to use web standards for the browser chrome, this is not a new development. Because Gecko supports web standards. And Gecko has been used for the browser UI for years. There is nothing particular to Servo here. There's nothing particular to Rust. Using standardized web tech for the "window chrome" is not "in the realm of possibility". It is possible. Full stop. It has never not been the case.
- SahAssar 7y ago
  I'll happily "loose" this whatever this discussion is if I'm wrong (but the "win" reference is now removed from your comment) but the basic idea is: 1. Servo supports many web standards, not XUL 2. The firefox UI used to be built in XUL 3. The firefox UI is now not built on XUL, but rather on web standards This means that the firefox UI can now be rendered by servo or similar components. That's basically the parent comment. If you disagree with any of those facts that's an interesting discussion, but I think you think that somebody said that the firefox UI could not be built on gecko previously, which nobody said.
  - cxr 7y ago
    So what we're dealing with here is Mitch Hedberg's "I used to do drugs" bit, only you're not joking.

cxr 7y ago

Funny, I feel the exact same way. > IIRC you can't render XUL strictly with web components or anything that would be called "web" > use [Servo] and web standards for the browser chrome. Geez, this is excruciating. If you want to use web standards for the browser chrome, this is not a new development. Because Gecko supports web standards. And Gecko has been used for the browser UI for years. There is nothing particular to Servo here. There's nothing particular to Rust. Using standardized web tech for the "window chrome" is not "in the realm of possibility". It is possible. Full stop. It has never not been the case.

SahAssar 7y ago
I'll happily "loose" this whatever this discussion is if I'm wrong (but the "win" reference is now removed from your comment) but the basic idea is: 1. Servo supports many web standards, not XUL 2. The firefox UI used to be built in XUL 3. The firefox UI is now not built on XUL, but rather on web standards This means that the firefox UI can now be rendered by servo or similar components. That's basically the parent comment. If you disagree with any of those facts that's an interesting discussion, but I think you think that somebody said that the firefox UI could not be built on gecko previously, which nobody said.
- cxr 7y ago
  So what we're dealing with here is Mitch Hedberg's "I used to do drugs" bit, only you're not joking.