Bug 257686
Summary: | Remove 'input.increment' since not in Web-Spec | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
Component: | Forms | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | akeerthi, annevk, cdumez, karlcow, rniwa, webkit-bug-importer, wenson_hsieh |
Priority: | P2 | Keywords: | BrowserCompat, InRadar, WPTImpact |
Version: | Safari Technology Preview | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=257687 https://bugs.webkit.org/show_bug.cgi?id=195818 |
Ahmad Saleem
Hi Team,
It is not spec'd as per: https://github.com/whatwg/html/issues/667
We are failing this test and we can get rid of 'incremental' by removing it from IDL file and also remove test added by following commit:
Commit: https://github.com/WebKit/WebKit/commit/bd4d5f416c383acadd1c036f35fabba22b45aa31
and change expectation of following WPT test:
https://wpt.fyi/results/html/semantics/forms/historical.html?label=master&label=experimental&aligned&q=%2Fhtml%2Fsemantics%2Fforms%2Fhistorical.html
WPT Test Live Link: http://wpt.live/html/semantics/forms/historical.html
Just wanted to raise so we can fix it.
Thanks!
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Anne van Kesteren
We have this failure in common with Chromium. Are they planning on removing it?
Ahmad Saleem
(In reply to Anne van Kesteren from comment #1)
> We have this failure in common with Chromium. Are they planning on removing
> it?
Chrome Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=690143
Chrome has removed internal usage and also added hooks to measure the usage via telemetry but their stats usage for ‘incremental’ are as follow:
https://chromestatus.com/metrics/feature/timeline/popularity/25
I think we can remove ‘incremental’ more easily compared to ‘search’ event.
Radar WebKit Bug Importer
<rdar://problem/110593059>
Ahmad Saleem
PR Attempt - https://github.com/WebKit/WebKit/pull/14701
*** This bug has been marked as a duplicate of bug 195818 ***