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 x=x pattern in HTML is generally used as a way to allow XML serializations (i.e. "XHTML") to do boolean attributes. I.e. instead of the simple <div checked>, you'd do <div checked="checked">, because XML does not allow value-less attributes.
We should probably avoid using this pattern for a non-boolean attribute, as it will confuse people.
Ideas:
Rename the attribute. (E.g. toplayerbehavior=popup or toplayer=popup.)
Rename the value. (E.g. popup=default, popup=onlyone.)
Have no value, and just a state. (So you'd do <div popup> with no value to get this behavior.)
I imagine there's going to be a general bikeshedding fest on popup/hint/async, but I just wanted to note this as a relatively high-priority consideration in that bikeshed.
The text was updated successfully, but these errors were encountered:
The
x=x
pattern in HTML is generally used as a way to allow XML serializations (i.e. "XHTML") to do boolean attributes. I.e. instead of the simple<div checked>
, you'd do<div checked="checked">
, because XML does not allow value-less attributes.We should probably avoid using this pattern for a non-boolean attribute, as it will confuse people.
Ideas:
toplayerbehavior=popup
ortoplayer=popup
.)popup=default
,popup=onlyone
.)<div popup>
with no value to get this behavior.)I imagine there's going to be a general bikeshedding fest on popup/hint/async, but I just wanted to note this as a relatively high-priority consideration in that bikeshed.
The text was updated successfully, but these errors were encountered: