Search element proposal

View project on GitHub

What went wrong in the search HTML element’s standardization

Author: Kaleidea, seasoned software architect, volunteer contributor (individual workstream participant).

I’ve worked 2 months on researching and implementing in 3 browsers the proposed <search> element so that the proposal best addresses developer needs and implementation constraints. I’ve invested an order of magnitude more effort than other participants.

Despite all the great work that’s done at the WHATWG, I’ve had a very counterproductive experience. During the standardization I’ve encountered numerous issues:

  • a lack of proper procedure
  • lack of research
  • ignoring developer feedback
  • uncollaborative behavior, lack of professionalism
  • suppression and censorship

Due to authority, the issues couldn’t be resolved within the WHATWG. This is the detailed report of what happened in 3 months.

Table of contents

  1. Standardization errors
    1. Inappropriate procedure
    2. Speculation instead of research
    3. Contempt towards developers
    4. W3C Design Principle violation
  2. Why is there disagreement?
    1. Lack of research
    2. Miscommunication
    3. Ignorance
    4. What led to this outcome?
  3. Conduct issues
    1. Suppression
    2. Abuse of authority
    3. Personal note