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
meta http-equiv is just used to specify a header, so you should be able to specify any header you need to without getting a validation error in the w3 validator and having the page being considered invalid HTML code.
I do not see the need to limit the headers that are allowed to just three.
I propose allowing any value for attribute "http-equiv" and any value for attribute "content" when http-equiv is used, this way any header can be used without a validation error and having the code be considered invalid.
If it is a valid header you should be allowed to specify it using the meta tag. Why not?
There are many times where webmasters need to use the meta tag to specify headers other then the three allowed in the current HTML5 standard.
Thanks,
Jacob Persico
The text was updated successfully, but these errors were encountered:
Unfortunately, it doesn't actually set a HTTP header. That was the envisioned functionality, but it doesn't work like that in practice. That's why there are limitations.
Not sure what you mean with "just three" by the way, there's seven pragma directives defined by the standard and five of them are currently conforming.
meta http-equiv is just used to specify a header, so you should be able to specify any header you need to without getting a validation error in the w3 validator and having the page being considered invalid HTML code.
I do not see the need to limit the headers that are allowed to just three.
I propose allowing any value for attribute "http-equiv" and any value for attribute "content" when http-equiv is used, this way any header can be used without a validation error and having the code be considered invalid.
If it is a valid header you should be allowed to specify it using the meta tag. Why not?
There are many times where webmasters need to use the meta tag to specify headers other then the three allowed in the current HTML5 standard.
Thanks,
Jacob Persico
The text was updated successfully, but these errors were encountered: