2 ms·
Interesting. So the browser-compatibility section is not crowd-sourceable. I never read it, though. It does appear that there is no incentive for a browser engi
by renewiltord 6y ago
Interesting. So the browser-compatibility section is not crowd-sourceable. I never read it, though. It does appear that there is no incentive for a browser engine to report that they are incompatible with something, only that they are compatible with something, but perhaps doing the latter implicitly implies through omission those for whom they are incompatible so that degenerates to "browser vendors will not report compatibility".
So be it. I think the rest is standards translation plus examples.
For this sort of thing, content isn't king, content is pawn. Back to w3schools or whatever, I suppose. Not the end of the world.
I think if it came to it, this could be BountySourced (or whatever the acceptable solution is now) and just suck up the fact that we won't have compatibility. With Evergreen browsers that's a moving target anyway.