Summary: | Support snapping, ticks for <input type="range"> | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Peter Kasting <pkasting> | ||||
Component: | Forms | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | cmarcelo, hyatt, ian, jonlee, michelangelo, mike, ravi.kasibhatla, tkent, webkit-bug-importer, webmaster | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Bug Depends on: | 27450, 27451 | ||||||
Bug Blocks: | 19264 | ||||||
Attachments: |
|
Description
Peter Kasting
2009-03-19 14:27:21 PDT
Created attachment 28763 [details]
Testcase
Hixie says: Draw tickmarks as given in list="". If no list="", draw them for step="", unless step has been set to "any". Hyatt says: Bah, didn't mean to submit that yet. Anyway, Hyatt says: Don't want ticks by default. Perhaps also no ticks for step=1. My proposal: Do what Hixie says, but also don't draw tickmarks if we don't have enough room. Assuming 1-px ticks, you'd need 2n + 1 pixels or more. If the theme only goes down to k-px ticks, we'd probably want k(2n + 1) free pixels; below that, no tickmarks + no snapping. Hopefully, this avoids breaking too many existing Mac widgets that don't want tickmarks, e.g. the Safari RSS widget, because they'd fail the 2n + 1 test. Is this issue still valid? If yes, I would like to propose a patch for the same. (In reply to comment #6) > Is this issue still valid? It's not closed and no one has commented otherwise, so assume yes. (In reply to comment #6) > Is this issue still valid? If yes, I would like to propose a patch for the same. Yes. I think Comment #2 to #4 are reasonable. This was done as <datalist> support. |