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
These should match :enabled, but currently do not:
li elements that are children of menu elements, and that have a child element that defines a command, if the first such element's Disabled State facet is false (not disabled)
(Similarly for :disabled with Disabled State facet is true (disabled))
... if its disabled attribute is set, or if it is a descendant of a fieldset element whose disabled attribute is set and is not a descendant of that fieldset element's first legend element child, if any.
The last part was skipped, so the current implementation is:
... if its disabled attribute is set, or if it is a descendant of a fieldset element whose disabled attribute is set
The text was updated successfully, but these errors were encountered:
None of the specifications linked from the Mozilla documentation mention these cases.
Moreover, the two linked specifications which do detail what should be considered :enabled or :disabled, which are the HTML5 specification and the HTML Living Standard, seem to provide a definition that is simpler than our current implementation.
@redapple, @kmike, @dangra What should we do? Should we follow the living standard? Should we follow the HTML5 standard? Should we make it possible to select which standard to follow?
cssselect's implementation does not match the spec and it also does not match the implementation in Chrome and Firefox where input:enableddoes match the hidden input element.
These should match
:enabled
, but currently do not:(Similarly for
:disabled
with Disabled State facet is true (disabled))Form elements should be considered disabled
The last part was skipped, so the current implementation is:
The text was updated successfully, but these errors were encountered: