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
The thing is, the new <meta charset="utf-8"> is designed to be backwards compatible. Don't see the reason to use both. Plus, and more importantly, the Standard explicitly states that
A document must not contain both a meta element with an http-equiv attribute in the encoding declaration state (http-equiv="content-type") and a meta element with the charset attribute present.
So doesn't it violate the standard? Or did I misinterpret what the standard is saying?
The text was updated successfully, but these errors were encountered:
In
default.hbs
,The thing is, the new
<meta charset="utf-8">
is designed to be backwards compatible. Don't see the reason to use both. Plus, and more importantly, the Standard explicitly states thatSo doesn't it violate the standard? Or did I misinterpret what the standard is saying?
The text was updated successfully, but these errors were encountered: