Bug 130719
| Summary: | Web Inspector: AXI: add support for range values | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | James Craig <jcraig> |
| Component: | Web Inspector | Assignee: | Aaron Chu <aaron_chu> |
| Status: | NEW | ||
| Severity: | Normal | CC: | graouts, inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
James Craig
Will use these methods and potentially more.
AccessibilityObject::supportsRangeValue()
AccessibilityNodeObject::valueDescription() (aria-valuetext)
AccessibilityNodeObject::valueForRange()
AccessibilityNodeObject::maxValueForRange()
AccessibilityNodeObject::minValueForRange()
AccessibilityNodeObject::stepValueForRange()
AccessibilityNodeObject::isIndeterminate()
UI for this could be compacted nicely. I think this would only be one or two rows in the sidebar.
Some thoughts:
* Ignore default min/max values (0/1) and common percentage min/max (0/100)
* Those are available in the node as attrs or defaults; just list those values as percent on sliders.
* Where necessary and if possible, list min/value/max and step on same line.
Examples:
Range Value: indeterminate
Range Value: 60%
Range Value: 3.5 of 1/5 (Step: 0.5)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/16419777>