-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
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
Search element specification with form functionality #7382
Conversation
Changes: <span><code>form</code> element pointer</span> -> <span><code data-x="">form</code> element pointer</span>
…ta-x=""`) Changes: <span><code data-x="form">form</code> element pointer</span> -> <span><code data-x="">form</code> element pointer</span>
Changes: <code>form</code> elements -> <span data-x="concept-form">forms</span> the <code>form</code> element -> <span data-x="concept-form">forms</span>
Changes: <code>form</code> element -> <span data-x="concept-form">form</span>
Changes: <code>form</code> element -> <span data-x="concept-form">form</span> <code>form</code> elements -> <span data-x="concept-form">forms</span>
Changes: <code>form</code> element <var>form</var> -> <span data-x="concept-form">form</span> <var>form</var>
Changes: <code>form</code> element -> <span>form owner</span>
Changes: <code>form</code> -> <span data-x="concept-form">form</span>
Changes: <code>form</code> element -> <span data-x="concept-form">form</span> (<codeform</code> or <code>search</code> element)
Changes: <code>form</code>, -> <code>form</code>, <code>search</code>, , or <code>form</code> -> <code>form</code>, or <code>search</code>
Changes: and <code>form</code> -> <code>form</code>, and <code>search</code> <code>form</code> -> <code>form</code> and <code>search</code>
Changes: <code>form</code> elements -> <span data-x="concept-form">forms</span> (<code>form</code> or <code>search</code> elements)
…ustom elements" section In this section form refers to either a `form` or a `search` element.
In this section form refers to either a `form` or a `search` element.
…bsections In this section form refers to either a `form` or a `search` element.
Changes: Any form starts with a <code>form</code> element -> Any <span data-x="concept-form">form</span> starts with a <code>form</code> or <code>search</code> element expected -> expected, but not as a descendant of another <code>form</code> or <code>search</code> element. <code>form</code> element -> <code>form</code> or <code>search</code> element <code>form</code> elements -> <code>form</code> and <code>search</code> elements
Defines: - attr-search-action Amends: - attr-fs-action - attr-fs-formaction
Defines: - attr-aria-role-search Credit for the explainer and examples: @scottaohara
As discussed in whatwg/sg#93 it's currently not possible to accept pseudonymous contributions. The SG is looking into this, but I suspect it will take quite a while before that has meaningfully progressed. |
Thank you for the reminder, not a problem at this stage. It seems there is a solution: what was necessary for you to approve PhistucK 2 years ago? whatwg/participant-data@9056efb |
It sounds like whatwg/sg#93 didn't go so well... |
This proposal was rejected; the search element that landed in the spec was instead https://html.spec.whatwg.org/#the-search-element. Thanks for the reminder to close this PR. |
Credit for the explainer and examples goes to @scottaohara, only minor adjustments were made.
Proposal
Implementations (proof-of-concept)
Specification (generated)
action
attrSpecification source
<search>
element to tag listsDesign decisions
<search>
is implemented byHTMLFormElement
.action
attribute is not set then form submission is disabled (method=dialog
still closes an ancestor dialog).action=""
attribute is valid - contrary to<form>
-, behaves as ifaction
is unset on a<form>
: submits to the document's base URL.<search>
as a<form>
: nesting of<search>
and<form>
is invalid in any combination. Invalid DOM with nesting can still be constructed with JS, behaves as nestedform
s do.<search>
cannot be a shadow root:.attachShadow()
is not allowed (like<form>
, but unlike<div>
). (MDN)Prerequisites
(See WHATWG Working Mode: Changes for more details.)
/acknowledgements.html ( diff )
/common-dom-interfaces.html ( diff )
/custom-elements.html ( diff )
/dom.html ( diff )
/form-control-infrastructure.html ( diff )
/form-elements.html ( diff )
/forms.html ( diff )
/index.html ( diff )
/indices.html ( diff )
/infrastructure.html ( diff )
/input.html ( diff )
/interaction.html ( diff )
/interactive-elements.html ( diff )
/links.html ( diff )
/obsolete.html ( diff )
/parsing.html ( diff )
/rendering.html ( diff )
/semantics-other.html ( diff )
/semantics.html ( diff )
/syntax.html ( diff )
/window-object.html ( diff )