Intent to Deprecate and Remove: 'results' attribute for <input type=search>

136 visualizzazioni
Passa al primo messaggio da leggere

TAMURA, Kent

da leggere,
26 feb 2016, 00:56:1726/02/16
a blink-dev
Contact emails

Spec
None.  A WebKit extension.

Summary
In Blink, 'results' attribute just adds a magnifier icon to an INPUT field.  It's a cosmetic feature.
In desktop Safari, it controls how many submitted queries are shown in a popup opened by clicking the magnifier icon.
This is a WebKit-extension, and it seems no one tried to standardize it.

We'd like to deprecate this attribute in M51, and remove it in M53.

Demo link
data:text/html,<input type=search results>

Motivation
It's a WebKit extension.

Interoperability risk
Firefox: Not implemented.
Edge: Not implemented.
Safari: Shipped for years
Web developers: No signals

Compatibility risk
The usage is about 0.04%.  However, because this is just a cosmetic feature in Google Chrome, it should be safe to remove it.

Ongoing technical constraints
We had to relax OSX sandbox only for 'results' attribute.  See crbug.com/508935 and crbug.com/505836.  We can avoid this issue by drawing an image ourselves.  However, investing in a WebKit-only feature is not reasonable.

Was this feature supported on all six Blink platforms (Windows, Mac, Linux,
Chrome OS, Android, and Android WebView)? Yes or no.
Yes.

OWP launch tracking bug

Link to entry on the Chrome Platform Status

Requesting approval to remove?
Yes.

--
TAMURA Kent
Software Engineer, Google





Jochen Eisinger

da leggere,
26 feb 2016, 00:59:0326/02/16
a TAMURA, Kent, blink-dev

lgtm1

PhistucK

da leggere,
26 feb 2016, 04:25:4426/02/16
a Jochen Eisinger, TAMURA, Kent, blink-dev
This actually seems very useful.
And while it is a cosmetic feature, when it is used - it does indicate that a certain text field is actually a search field to the user. Removing that may cause user pain.

I actually wish this would be standardized. A lot of websites use this pattern (a magnifying glass on one side and a clear button on the other side when text exists) and removing this support will require some work from the developers as well as the designers (which can take a while, or be not as lightweight as you think).

Perhaps just try and standardize this?


PhistucK

lgtm1

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

Philip Jägenstedt

da leggere,
26 feb 2016, 05:18:0126/02/16
a PhistucK, Jochen Eisinger, TAMURA, Kent, blink-dev
LGTM2, I've stumbled across this a few times and always got an itch to remove it.

I don't think trying to standardize this as-is makes much sense, if it's currently difficult to put an icon of your choosing inside an input element, then that or something even more generic would be the feature to standardize.

Chris Harrelson

da leggere,
26 feb 2016, 13:37:0626/02/16
a Philip Jägenstedt, PhistucK, Jochen Eisinger, TAMURA, Kent, blink-dev
LGTM3

TAMURA, Kent

da leggere,
28 feb 2016, 18:35:2528/02/16
a PhistucK, blink-dev
IMO, we shouldn't standardize it.  Using WebComponents is a right direction.
Rispondi a tutti
Rispondi all'autore
Inoltra
0 nuovi messaggi