Open Bug 1088476 Opened 11 years ago Updated 3 years ago

Poor UX when tabbing through element attributes

Categories

(DevTools :: Inspector, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: mgcook89, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141013200257 Steps to reproduce: 1. Open inspector panel 2.For an element with multiple attributes, double-click the first attribute to begin editing it. (ie, for '<div id="navigation" class="sticky"></div>' double-click 'navigation') 3. Press tab a few times Actual results: First tab press moves carat to end of current selection Second tab disables edit mode but keeps focus on current attribute Next tab moves focus to second attribute, but you can't type to edit straight away - must press enter first Expected results: I think the current Firebug (2.0.4) gets this spot on. When editing an attribute, tab will cycle through the remaining keys/values individually, keeping edit mode enabled, and will also construct a new attribute (with placeholder '=' and '""') when you tab off the end.
Component: Untriaged → Developer Tools: Inspector
Bug 911148 handles one component of this, keeping edit mode while tabbing through. That leaves two things from the desired results described here that will still need handling after that bug is completed: 1) It's still two tab presses to go through each attribute: First tab press moves caret to end of current selection. Second tab moves to next attribute -- still in edit mode. 2) When you get to the end of the list of attributes, you can type in a new attribute, but it's a blank space (no placeholder text)
Inspector bug triage. Filter on CLIMBING SHOES. Reproduced on latest nightly. Current status is the one described in comment 1.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Priority: -- → P3
Hardware: x86_64 → All
Version: 33 Branch → Trunk
Product: Firefox → DevTools
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.