(In reply to :Gijs (he/him) from comment #14) > > If MDN is wrong, please fix it or set keyword. > > MDN isn't wrong, it's more that it describes current behaviour (warts and all, just look at some of the stuff it used to have about IE if that's your jam), and shouldn't be used to determine whether Gecko's current behaviour is **correct** per the specification / web-compatible. > I added more info about the header/attribute behaviour to MDN. Thanks! With "wrong" I meant MDN didn't state reality before (Chromium vs. Firefox vs. spec) and especially after this bugfix. That said, these days MDN actually descibes specced behaviour und even has links to bug reports if browsers don't follow. There is signifant input from Google/Chromium folks.
Bug 1658877 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to :Gijs (he/him) from comment #14) > > If MDN is wrong, please fix it or set keyword. > > MDN isn't wrong, it's more that it describes current behaviour (warts and all, just look at some of the stuff it used to have about IE if that's your jam), and shouldn't be used to determine whether Gecko's current behaviour is **correct** per the specification / web-compatible. > I added more info about the header/attribute behaviour to MDN. Thanks! With "wrong" I meant MDN didn't state reality before (Chromium vs. Firefox vs. spec) and especially after this bugfix. That said, these days MDN actually describes specced behaviour and even has links to bug reports if browsers don't follow. There is signifiant input from Google/Chromium folks.