4 ms·

Hopefully the URL spec (https://url.spec.whatwg.org https://url.spec.whatwg.org) is helpful here in finding other potentially unsafe behaviours that browsers ha

Hopefully the URL spec (https://url.spec.whatwg.org https://url.spec.whatwg.org) is helpful here in finding other potentially unsafe behaviours that browsers have, though given much of it seems to be dealing with the fact that urllib.urlparse doesn't match what browsers do in many, many ways it's probably of limited help. (Nobody really implements it yet; it's just an attempt at standardising rough intersection semantics of what browsers currently do. Eventually, however, it should suffice, once legacy browsers eventually die.)

kuschku 10y ago
That URL spec is just "this is what chrome does, everyone repeat that". They’re unwilling to modify anything, or standardize anything, but just want to cement the current piece of shit that URL parsing it for the future.
- gsnedders 10y ago
  Given Chrome Canary currently fails a large number of tests, it seems like it's hardly just "this is what chrome does, everyone repeat that".
  - kuschku 10y ago
    Because the standard was changed to clean a bit of the stuff Google did up. But WHATWG only changes standards to include more, never to include less.
- jcranmer 10y ago
  WHATWG standards are generally formed by starting from what the 4 major browsers (Chrome, Firefox, IE (Edge), Safari) do. Anything that is done in common by all of them gets implemented no problem. It's when they all differ that the editor(s) tries to come up with more reasoned algorithms.
  - kuschku 10y ago
    Which is not really ideal. Standards aren’t about documenting what is, but about defining what will be.
  - dragonwriter 10y ago
    > WHATWG standards are generally formed by starting from what the 4 major browsers (Chrome, Firefox, IE (Edge), Safari) do. I thought WHATWG standards are formed by starting with what the four major browser vendors agree to do, not what they currently do (though usually at least one has an implementation before something gets proposed for standardization.)

kuschku 10y ago

That URL spec is just "this is what chrome does, everyone repeat that". They’re unwilling to modify anything, or standardize anything, but just want to cement the current piece of shit that URL parsing it for the future.

gsnedders 10y ago
Given Chrome Canary currently fails a large number of tests, it seems like it's hardly just "this is what chrome does, everyone repeat that".
- kuschku 10y ago
  Because the standard was changed to clean a bit of the stuff Google did up. But WHATWG only changes standards to include more, never to include less.
jcranmer 10y ago
WHATWG standards are generally formed by starting from what the 4 major browsers (Chrome, Firefox, IE (Edge), Safari) do. Anything that is done in common by all of them gets implemented no problem. It's when they all differ that the editor(s) tries to come up with more reasoned algorithms.
- kuschku 10y ago
  Which is not really ideal. Standards aren’t about documenting what is, but about defining what will be.
- dragonwriter 10y ago
  > WHATWG standards are generally formed by starting from what the 4 major browsers (Chrome, Firefox, IE (Edge), Safari) do. I thought WHATWG standards are formed by starting with what the four major browser vendors agree to do, not what they currently do (though usually at least one has an implementation before something gets proposed for standardization.)