We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This should haven after #1454 lands, as that removes the term "required owned element".
There are many uses of "owned elements" which should probably be reconsidered. For example, in spinbutton:
Authors MAY create a spinbutton with children or owned elements, but MUST limit those elements to a textbox and/or two buttons.
Should we simply say "with accessibility children" or "with children" or (maybe) "with owned elements"?
Additionally, "owning element" is not used in the spec, except in tooltip where it's meaning is not even the definition of "owning element":
The tooltip typically becomes visible, after a short delay, in response to a mouse hover, or after the owning element receives keyboard focus
The text was updated successfully, but these errors were encountered:
oops this is a duplicate of: #1161
Sorry, something went wrong.
No branches or pull requests
This should haven after #1454 lands, as that removes the term "required owned element".
There are many uses of "owned elements" which should probably be reconsidered. For example, in spinbutton:
Should we simply say "with accessibility children" or "with children" or (maybe) "with owned elements"?
Additionally, "owning element" is not used in the spec, except in tooltip where it's meaning is not even the definition of "owning element":
The text was updated successfully, but these errors were encountered: