Intent to Deprecate and Remove: HTMLOptionsCollection.remove(element)

43 views
Skip to first unread message

Philip Jägenstedt

unread,
Jul 29, 2014, 5:34:13 PM7/29/14
to blink-dev

Primary eng (and PM) emails

phi...@opera.com


Summary

Remove HTMLOptionsCollection.remove(element)


Motivation

Removing by element instead of index is a WebKit/Blink quirk, the spec only has remove(index):

http://whatwg.org/html#htmloptionscollection


It's not even an optimization, it's implemented as remove(element.index).


This ad-hoc test has all other browsers agreeing on non-support:

http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3089

Compatibility Risk

Insignificant.


Alternative implementation suggestion for web developers

Use select.options.remove(element.index) or just element.remove().


Usage information from UseCounter

http://www.chromestatus.com/metrics/feature/timeline/popularity/398


Available in M36. Usage rounds to zero.

Entry on chromestatus.com, crbug.com, or MDN

None.


Requesting approval to remove too?

Yes.

Adam Barth

unread,
Jul 29, 2014, 5:49:09 PM7/29/14
to Philip Jägenstedt, blink-dev
LGTM

Eric Seidel

unread,
Jul 29, 2014, 6:17:02 PM7/29/14
to Adam Barth, Philip Jägenstedt, blink-dev
lgtm

Dimitri Glazkov

unread,
Jul 29, 2014, 6:17:20 PM7/29/14
to Eric Seidel, Adam Barth, Philip Jägenstedt, blink-dev
lgtm3
Reply all
Reply to author
Forward
0 new messages