Skip to content

Add <meta name="responsive-embedded-sizing">#12444

Open
kojiishi wants to merge 1 commit into
whatwg:mainfrom
kojiishi:responsive-embedded-sizing
Open

Add <meta name="responsive-embedded-sizing">#12444
kojiishi wants to merge 1 commit into
whatwg:mainfrom
kojiishi:responsive-embedded-sizing

Conversation

@kojiishi
Copy link
Copy Markdown

@kojiishi kojiishi commented May 13, 2026

This adds <meta name="responsive-embedded-sizing"> as an immutable standardized name.

This is used by the CSS responsive embedded sizing flag.

(See WHATWG Working Mode: Changes for more details.)


/dom.html ( diff )
/infrastructure.html ( diff )
/semantics.html ( diff )

This adds `<meta name="responsive-embedded-sizing">` as an immutable standardized name.

This is used by the CSS [responsive embedded sizing flag].

[responsive embedded sizing flag]: https://drafts.csswg.org/css-sizing-4/#document-responsive-embedded-sizing-flag
@kojiishi
Copy link
Copy Markdown
Author

@mtrootyy
Copy link
Copy Markdown

If either name, http-equiv, or itemprop is specified in meta element, then the content attribute must also be specified.
If "responsive-embedded-sizing" is specified to value of name attribute of mata element, what is specfied to value of content attribute of this meta element?

@miketaylr
Copy link
Copy Markdown
Member

https://html.spec.whatwg.org/#the-meta-element

If either name, http-equiv, or itemprop is specified, then the content attribute must also be specified. Otherwise, it must be omitted.

But just below:

If a meta element has a name attribute, it sets document metadata.... If a meta element has no content attribute, then the value part of the metadata name-value pair is the empty string.

So meta with name and without content is allowed (but, imho it's a bit confusing for HTML to use must in "this must be specified, otherwise it must not be specified" instead of may?)

@mtrootyy
Copy link
Copy Markdown

mtrootyy commented May 18, 2026

If a meta element has no content attribute, then the value part of the metadata name-value pair is the empty string.

The above specifications are for user agents, not for authors.
Regardless of how the user agent processes it, author must comply with the following specifications.

If either name, http-equiv, or itemprop is specified, then the content attribute must also be specified.

Comment thread source
the user agent must run the following algorithm:</p>

<ol>
<li><p>If <var>element</var> is not inserted by the parser, then return.</p></li>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This doesn't seem like a good idea. This will just encourage people to use document.write() instead of tree manipulation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants