28225 2015-03-16 10:37:39 +0000 Do we really want getting <input type=image>.selectionDirection to throw? 2016-04-06 10:21:29 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED https://html.spec.whatwg.org/#textFieldSelection P3 normal Unsorted 1 contributor ian annevk ian mike zcorpan contributor oldest_to_newest 118618 0 contributor 2015-03-16 10:37:39 +0000 Specification: https://html.spec.whatwg.org/multipage/forms.html Multipage: https://html.spec.whatwg.org/multipage/#textFieldSelection Complete: https://html.spec.whatwg.org/#textFieldSelection Referrer: https://html.spec.whatwg.org/multipage/embedded-content.html Comment: Do we really want getting <input type=image>.selectionDirection to throw? [[ For input elements, calling these methods while they don't apply, and getting or setting these attributes while they don't apply, must throw an InvalidStateError exception. ]] I noticed this because w(<input type=image>) in Live DOM Viewer hits this exception since it enumerates the attributes and prints the values. The forms API in general is pretty lenient for this kind of thing, so you can check an attribute for any control in a collection without first checking that the control is one where the attribute applies (e.g. type on textarea). Posted from: 94.234.170.175 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.74 Safari/537.36 OPR/28.0.1750.36 (Edition beta) 119098 1 ian 2015-03-30 23:08:18 +0000 Yeah there's an API subset that's intentionally supported on everything in form.elements. But I'm not sure what it would mean for selectionDirection to work on everything. In particular, I think people would find it weirder that it returned something but didn't match reality on <input type=number>, than if it threw. 119138 2 zcorpan 2015-03-31 14:21:51 +0000 How about making it return null when it does not apply? 119324 3 ian 2015-04-07 22:33:35 +0000 I guess that could work. 125632 4 annevk 2016-03-25 13:24:23 +0000 This already works across Firefox and Chrome, do we really want to rock the boat here? 125732 5 zcorpan 2016-04-06 08:46:37 +0000 https://github.com/nwjs/nw.js/issues/2934 https://bugs.webkit.org/show_bug.cgi?id=111476 (tangentially related but changing to null would make this moot) https://bugzilla.mozilla.org/show_bug.cgi?id=746906 http://stackoverflow.com/questions/13997203/qunit-comparing-hidden-inputs-typeerror-selectiondirection-on-input It appears that throwing is both surprising and causes problems, so I think would be good to change. 125733 6 annevk 2016-04-06 08:50:15 +0000 I guess, if we can get implementers on board. Mounir seemed pretty skeptical. 125734 7 zcorpan 2016-04-06 10:21:29 +0000 https://github.com/whatwg/html/pull/1006