Security implications? Does this strip away a layer of security?
The Firefox UI Is Now Built with Web Components
11–20 of 260 posts
Re: The Firefox UI Is Now Built with Web Components
#12Security implications? Does this strip away a layer of security?
So this should help Firefox be more secure, by decreasing attack surface.
Re: The Firefox UI Is Now Built with Web Components
#13People seem to love laggy web-sights, let's port the lag into the browser's UI!
Re: The Firefox UI Is Now Built with Web Components
#14Remember when a tab freezing didn't make Firefox's UI chrome unresponsive? I do, too.
Web 4.0 is the internet of race conditions. Thanks, javascript everywhere.
Re: The Firefox UI Is Now Built with Web Components
#15Re: The Firefox UI Is Now Built with Web Components
#16Security implications? Does this strip away a layer of security?
Why would there be security implications?
Especially when receiving generally untrusted input from the internet (websites, extensions, web-workers in this case) and you're suppose to display/use that somehow.
Re: The Firefox UI Is Now Built with Web Components
#17People seem to love laggy web-sights, let's port the lag into the browser's UI!
Re: The Firefox UI Is Now Built with Web Components
#18Re: The Firefox UI Is Now Built with Web Components
#19Security implications? Does this strip away a layer of security?
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.
Re: The Firefox UI Is Now Built with Web Components
#20I 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.