2 ms·
>How do specs fit into this if every browser is just a UI shell around chrome? The browser engine is open source. You can make changes and proposals with your
by charcircuit 3y ago
>How do specs fit into this if every browser is just a UI shell around chrome?
The browser engine is open source. You can make changes and proposals with your own fork. If you are making a browser for musicians you could try and advance the WebMIDI spec and add new functionality to it and then try to get it standardized. But as a browser developer you don't want to me spending your time implenting specs that other people have already implemented, but rather spending time working on things that improve your browser for your userbase.
- flagrant_taco 3y agoWhat you're describing is the opposite of the whole point of specifications. The aim wasn't to circle around a single implementation, it was to define feature specifications that would allow multiple vendors to build cross-compatable web browsers. What would be the point of open specifications if there was only a single implementation?
- charcircuit 3y ago>What would be the point of open specifications if there was only a single implementation? I never said there was? When you write the first implementation then there will only be a single implementation, but that's how counting works. 1 comes after 0. Anyone is free to write another implementation.