-
Notifications
You must be signed in to change notification settings - Fork 49.1k
Closed
Labels
Component: DOMStatus: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug
Description
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
When specifying inert={false}
on an element, React throws the following message:
Warning: Received `false` for a non-boolean attribute `inert`.
However, inert={undefined}
works fine as a replacement for false
, while inert=""
(empty string) provides an escape hatch as a truthy value.
What is the expected behavior?
The inert
attribute should be accepted as a boolean DOM attribute, as proposed by the HTML Standard.
jameswilson, MidnightDesign, benface, soluml, Nicolapps and 40 more
Metadata
Metadata
Assignees
Labels
Component: DOMStatus: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug