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 latest release adds the popover attribute with boolean as a supported type (see #4378). When setting this prop to a boolean value, I'd expect it to add or remove the popover attribute, but not set a value, like eg. the disabled prop. Instead it adds popover="true" or popover="false", stringifying the boolean value, like aria- attributes. This results in a warning from Chrome that the value is not allowed.
A workaround is to use the values "auto" and undefined to substitute for boolean true/false.
Describe the bug
The latest release adds the
popover
attribute withboolean
as a supported type (see #4378). When setting this prop to a boolean value, I'd expect it to add or remove thepopover
attribute, but not set a value, like eg. thedisabled
prop. Instead it addspopover="true"
orpopover="false"
, stringifying the boolean value, likearia-
attributes. This results in a warning from Chrome that the value is not allowed.A workaround is to use the values
"auto"
andundefined
to substitute for boolean true/false.Tested with Preact v10.22.0.
To Reproduce
test.html:
Steps to reproduce the behavior:
Found a 'popover' attribute with an invalid value. <div popover="true"></div>
Expected behavior
The above should render
<div popup></div>
.The text was updated successfully, but these errors were encountered: