They can still reject the proposal. Just because they’re built upon Chromium, doesn’t mean they need to utilise or retain every feature Google adds to it.
Any browser choosing not to implement this would not be trusted and any website choosing to use this API could therefore reject users from those browsers.
That is semantics that wont help the users. They still need to change browser to access their banks website if their bank is enforcing WEI. There is nothing “broken” in the technical sense, the website and browser will be incompatible with oneanother. The blame is clearly on the bank but what’s a single user gonna do if this becomes industry standard for banks?
(I am using banks as an example of a service you cant easily avoid, this would also be true for other important stuff like digitialized government access etc ect)
Forking would be insane because of how much code is in Chromium and how much work goes into maintaining it. The realistic thing to do is to keep doing what they’ve been doing: maintain a modified branch. WEI would just be one of many changes between Google’s version and other vendors’.
Brave and Vivaldi are both built on Chromium though…
They can still reject the proposal. Just because they’re built upon Chromium, doesn’t mean they need to utilise or retain every feature Google adds to it.
I think it’s not easy this time.
For sites that fully embrace the new web environment integrity procedure would that break chromium browsers like Brave too?
That would break websites, not browsers.
That is semantics that wont help the users. They still need to change browser to access their banks website if their bank is enforcing WEI. There is nothing “broken” in the technical sense, the website and browser will be incompatible with oneanother. The blame is clearly on the bank but what’s a single user gonna do if this becomes industry standard for banks?
(I am using banks as an example of a service you cant easily avoid, this would also be true for other important stuff like digitialized government access etc ect)
That’s was what I meant. Websites not functioning properly and informing users to use approved ones like Chrome or Edge.
If only Google supports this, the rest can fork it together.
Forking would be insane because of how much code is in Chromium and how much work goes into maintaining it. The realistic thing to do is to keep doing what they’ve been doing: maintain a modified branch. WEI would just be one of many changes between Google’s version and other vendors’.
So: a fork. It’s not unusual for a fork to regularly merge back the upstream changes while maintaining its own set of changes.