Skip to content

Explain that http-equiv has nothing to do with HTTP headers #11494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 28, 2025

Conversation

domenic
Copy link
Member

@domenic domenic commented Jul 28, 2025

Closes #7435. See also #2335 which discusses name="" vs. http-equiv="".


/semantics.html ( diff )

@domenic domenic added the clarification Standard could be clearer label Jul 28, 2025
Closes #7435. See also #2335 which discusses name="" vs. http-equiv="".
@domenic domenic force-pushed the http-equiv-discussion branch from 4ae5b10 to 0d3d825 Compare July 28, 2025 06:05
@domenic domenic mentioned this pull request Jul 28, 2025
9 tasks
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Modulo addressing the comment about the third paragraph.

<div class="warning" id="warning-http-equiv-unrelated-to-http-headers">
<p>Despite the name <code data-x="attr-meta-http-equiv">http-equiv</code>, pragma directives are
almost entirely unrelated to HTTP headers. Implementers and web developers are best off thinking
of them as entirely separate, and the name as being a historical accident.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thankfully we have "a hierarchy" as example in the style guide.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was still surprised that it was "an HTTP" instead of "a HTTP"...

<code>meta</code> similar to the model used by the <code
data-x="attr-meta-charset">charset</code> attribute. (Note that avoiding in-document pragmas is
often the better choice, since the DOM is mutable, and it's rarely a good idea to let pragmas be
applied or un-applied dynamically.)</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The mere fact of putting it in the node tree makes a policy mutable as you at least go from 0 to 1 during the lifetime of the document. I think that's worth clarifying here as that's often overlooked.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me know what you think of the new phrasing

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lovely, thanks!

@domenic domenic merged commit b6dd913 into main Jul 28, 2025
2 checks passed
@domenic domenic deleted the http-equiv-discussion branch July 28, 2025 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer
Development

Successfully merging this pull request may close these issues.

meta tag with attribute http-equiv has a small arbitrary limit on the headers that can be specified
2 participants