3 ms·
There was an attempt to address Mozilla's concerns[1], but Mozilla never responded, unfortunately. If the Mozilla community chooses not to respond, that might
by tytso 7y ago
There was an attempt to address Mozilla's concerns[1], but Mozilla never responded, unfortunately. If the Mozilla community chooses not to respond, that might cause people to consider whether or not their position should be given much weight.
[1] https://github.com/mozilla/standards-positions/issues/29#issuecomment-459547918 https://github.com/mozilla/standards-positions/issues/29#iss...
- RubenSandwich 7y agoWhat do you mean they never responded? They say they are working on a response[0]. Taking time to respond and informing the other party that it will take a while is not "never responded". [0] https://github.com/mozilla/standards-positions/issues/29#issuecomment-459605378 https://github.com/mozilla/standards-positions/issues/29#iss...
- tytso 7y ago3 months is a long time.... how long is someone supposed to wait for a response before you just move ahead? If the answer is "forever", it becomes trivial to perform a denial of service attack on a standard. Mozilla specifically said, "this is not high priority for us". If it's not high priority for them to respond, that's fine, but waiting forever doesn't seem like a reasonable thing to require.
- codedokode 7y agoI am against this standard. First, I want to see the real URL in the address bar. Second, I don't want Mozilla to spend resources to implement specification that is made by Google for its own purposes.