3 ms·
Mozilla's position on these specs is nicely outlined publicly and transparently as part of their standards-positions project: https://github.com/mozilla/standar
by lol768 3y ago
Mozilla's position on these specs is nicely outlined publicly and transparently as part of their standards-positions project: https://github.com/mozilla/standards-positions/issues/100 https://github.com/mozilla/standards-positions/issues/100
I'm kinda glad it's not implemented in my browser, to be honest, because the whole thing seems like a security nightmare.
It's a shame it impacts some hobby usecases, but I don't think this outweighs the reasoning set out on the GitHub issue.
- o11c 3y ago> I'm kinda glad it's not implemented in my browser, to be honest, because the whole thing seems like a security nightmare. You shouldn't look at the spec and think it's a security nightmare. Look at the history, so you can know it's a security nightmare.