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
{{ message }}
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
Apparently compatibility caseless matching is used due to legacy IE behavior, though browsers are pretty inconsistent in to what extent this matching is implemented. The current spec leaves it relatively undefined to avoid the problem. There is general consensus that having compatibility caseless matching is a can of worms, and we would prefer to remove it from the spec. Can implementations align on something else? What is the impact to web content? These are some of the question that should be resolved.
Used in:
<map name="..."> - the name value of a map
radio button name groups
The text was updated successfully, but these errors were encountered:
arronei
changed the title
Tighten up usages of "compatibilty caseless" comparisons used in the spec
Sync up usages of "compatibilty caseless" comparisons used in the spec
May 30, 2017
Cloned from bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16970
Apparently compatibility caseless matching is used due to legacy IE behavior, though browsers are pretty inconsistent in to what extent this matching is implemented. The current spec leaves it relatively undefined to avoid the problem. There is general consensus that having compatibility caseless matching is a can of worms, and we would prefer to remove it from the spec. Can implementations align on something else? What is the impact to web content? These are some of the question that should be resolved.
Used in:
<map name="...">
- the name value of a mapThe text was updated successfully, but these errors were encountered: