> 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.
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.
> 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.