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.
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:However,
inert={undefined}works fine as a replacement forfalse, whileinert=""(empty string) provides an escape hatch as a truthy value.What is the expected behavior?
The
inertattribute should be accepted as a boolean DOM attribute, as proposed by the HTML Standard.