Primary eng (and PM) emails
Link to “Intent to Deprecate” thread
None. I think we may skip deprecation because of low usage.
If we skip deprecation, I'm going to remove this feature just after M48 branch.
Summary
Drop img element from form-associated elements.
More concretely, remove the following two behaviors:
[1] form.foo returns an img element
[2] form.elements.foo returns an img element
I proposed a specification change, and concluded that we'll change the specification if Blink successfully remove the feature.
https://github.com/whatwg/html/issues/294
https://github.com/whatwg/html/pull/297
[1] https://html.spec.whatwg.org/multipage/forms.html#dom-form-nameditem IE, Firefox, Safari, Google Chrome support this.
[2] Non-standard WebKit quirk. Safari and Google Chrome support it.
Motivation
- This feature is not reasonable at all. Image is not a form control.
- Code maintenance burden. Form-association was a source of crash bugs, and img form-association is slightly different from form control form-association.
See https://github.com/whatwg/html/issues/294#issuecomment-152884108
Compatibility Risk
Low-to-middle.
+ Major browsers support it.
+ This is very long-standing feature. WebKit introduced it 11 years ago.
Note that neither HTML4 nor DOM Level 2 HTML doesn't define it.
+ In the worst case, JavaScript code stops by accessing undefined value.
- Usage is extremely low (See below).
Usage information from UseCounter
https://www.chromestatus.com/metrics/feature/timeline/popularity/246
OWP launch tracking bug
Entry on the feature dashboard
https://www.chromestatus.com/feature/5725368270979072
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
I double checked the internal usage - it's effectively 0 (but just enough above 0 to show that the UseCounter is indeed working <grin>). Given that, LGTM2. If the usage had been "low" but non-zero, I probably would have argued for a deprecation period.
On Mon, 02 Nov 2015 21:12:47 +0100, Rick Byers <rby...@chromium.org> wrote:I double checked the internal usage - it's effectively 0 (but just enough above 0 to show that the UseCounter is indeed working <grin>). Given that, LGTM2. If the usage had been "low" but non-zero, I probably would have argued for a deprecation period.Is it in the forms member array? I just realised that people like to access form elements by number and removing an element will reorder anything later.
Does the usecounter include all the cases when there is an image in the forms member array?
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
All of them sound very small and not risky, am I missing something?
--
Simon Pieters
Opera Software