| Summary: | Range and number inputs should reject increment and decrement by keyboard or mouse wheel if they are disabled or read-only | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Kent Tamura <tkent> | ||||
| Component: | Forms | Assignee: | Kent Tamura <tkent> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | abarth, adele, darin, dglazkov, eric, hamaji, webkit.review.bot | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| URL: | http://code.google.com/p/chromium/issues/detail?id=70740 | ||||||
| Attachments: |
|
||||||
|
Description
Kent Tamura
2011-01-25 17:39:11 PST
Created attachment 80150 [details]
Patch
Comment on attachment 80150 [details]
Patch
ok. Is this the typical way we handle disabled and readOnly for elements?
(In reply to comment #2) > ok. Is this the typical way we handle disabled and readOnly for elements? I think we have no other way. e.g. We can't skip all of key event handling in HTMLInputElement.cpp because we'd like to handle ⌘-C or Ctrl-c even if the element is disabled or read-only. Comment on attachment 80150 [details] Patch Clearing flags on attachment: 80150 Committed r76662: <http://trac.webkit.org/changeset/76662> All reviewed patches have been landed. Closing bug. http://trac.webkit.org/changeset/76662 might have broken Leopard Intel Release (Tests) |