4 ms·

There's nothing in the spec that promises you a little "x" to clear the value: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/search https://d

by dak1 8y ago

There's nothing in the spec that promises you a little "x" to clear the value: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/search https://developer.mozilla.org/en-US/docs/Web/HTML/Element/in... Chrome also frequently attempts to cover up incorrect code with what it thinks the author probably meant. Firefox tends to be much better than Chrome at following the actual spec. I tend to develop primarily with Chrome first for some different reasons (ability to disable CORS, support for self-signed certs with WebSockets, and its better debugging of WS frames), but I always make sure to test later with Firefox and Safari, and occasionally find code that worked in Chrome, but doesn't elsewhere, and the reason is almost invariably always that Chrome didn't follow the spec.

Phillips126 8y ago
Fair enough about it not being in the spec. It does appear to be a part of Apples' "Human Interface Guidelines"[1], although these guidelines are pointed to native applications. It was just an unexpected regression that occurred during the rollout of iOS9 and is an example of one of the little nuances that caused me to do something different. I've had some other issues regarding scrolling and focus, but this one seemed to be easier to talk about. [1] https://developer.apple.com/design/human-interface-guidelines/ios/bars/search-bars/ https://developer.apple.com/design/human-interface-guideline...