You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[…] execute the rules for identifying an unknown MIME type with the sniff-scriptable flag equal to the inverse of the no-sniff flag and abort these steps.
In 7.1:
If the setting of the sniff-scriptable flag is not specified when calling the rules for identifying an unknown MIME type, the sniff-scriptable flag must default to unset.
From 7, and assuming that’s the only point in the specification that calls for 7.1, I understand that the sniff-scriptable flag should always be specified (as the opposite of no-sniff flag). If so, I think that paragraph from 7.1 should be removed or rephrased, for clarity.
The text was updated successfully, but these errors were encountered:
In 7, step 1:
In 7.1:
From 7, and assuming that’s the only point in the specification that calls for 7.1, I understand that the
sniff-scriptable
flag should always be specified (as the opposite ofno-sniff
flag). If so, I think that paragraph from 7.1 should be removed or rephrased, for clarity.The text was updated successfully, but these errors were encountered: