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
{{ message }}
Instantly share code, notes, and snippets.
Kaleidea
Seasoned software architect. No nonsense, just facts and reason. Time is too precious to waste on confusion.
<search> element with <form> functionality - draft implementation patch for Chromium Blink
Disclaimer
This is a draft implementation made in a rush in a few hours without prior knowledge of the codebase.
There was no time to build it. I heard I might need a buildfarm... Consequently it might not compile.
It is only meant to demonstrate the basic changes needed to implement the form-based search element.
Should the implementation of a hybrid element as defined above fall through, an alternative is to define 2 elements (<search> and <searchform>) for the 2 use-cases:
Implementing this is trivial by aliasing HTMLElement -> <search> and <form> -> <searchform>. Corner cases of nesting need no consideration, and the specification is a trivial "Uses HTMLFormElement, as defined for form elements". The trade-off is that two instead of one element specifications are added.
Should 2 elements find opposition, the proposal would be to favor the best practice:
This solution satisfies the original use-case defined as "people who don't want form behavior": <search> without the action attribute behaves as <div role=search>, the same as the original proposal.
Breakdown of individual form features:
Form submission is disabled if the action attribute is unspecified.
Autocomplete is not affected (it is already enabled by default for <input type=search>).
There is no form validation unless the developer explicitly sets it up.
There is no reset button unless the developer adds one.
`` is registered in document.forms, this has no effect unless the developer iterates `forms`, in which case this is expected.
Appeal to the WHATWG Steering Group about discourtesy and a non-inclusive standardization process for the proposed `<search>` element
Dear Steering Group members,
I'd like to raise concerns regarding my experience recently contributing to the ongoing standardization of the search element. I'm facing serious communication difficulties, misunderstandings and disrespectful comments. I'd like to ask for your attention and independent input to steer this discussion towards mutual understanding and an outcome that's inclusive to differing perspectives and practices.
The issue
There is a disagreement about the viability of extending the form element. To prove my point I've implemented the form-based search element: 29 lines changed for the key features, proving its viability and low implementation cost.
This input is not welcome, deliberations about it are not reciprocated. We are discussing incompatible concepts (reuse vs. duplication) and despite my attempts to clear up this misunderstanding, my reasoning is not
<search> element request with <form> functionality
Consider making the HTML <search> element an alias for <form> when the action attribute is specified
This proposal presents a novel approach to implementing the <search> element with improved API ergonomy and featuring the best practice usage for the little cost of 29 lines of code changed in Chromium Blink (draft, without tests).
This implementation disproves the prior assumption that aliasing the <form> element raises huge implementation costs, which assumption was the reason to oppose this feature.
Report of code of conduct violations by a WHATWG member
Dear Steering Group members,
Please confirm whether this and the previous complaint was received upon receiving this email.
The previously reported pattern of policy and code of conduct violations has continued, despite a complaint to the person at fault.
This is very unfortunate and I deeply regret that a prominent member of the WHATWG has to be reported.
Please take immediate action to restore a safe environment and to prevent damage to the WHATWG's image as an open, safe, welcoming and professional environment.
"Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back."