Closed
Bug 1352776
Opened 8 years ago
Closed 8 years ago
In put fields do not blur automatically when selecting a ::before pseudo element in the markup-view
Categories
(DevTools :: Inspector, defect, P3)
DevTools
Inspector
Tracking
(firefox55 fixed)
RESOLVED
FIXED
Firefox 55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: magicp.jp, Assigned: pbro)
Details
Attachments
(2 files)
[Steps to reproduce]
1. Start any versions Firefox
2. Go to about:home
3. Open Inspector > Computed
4. Select #aboutMozilla in markup
5. Click width/height on boxmodel-content > Edit box is enabled
6. Select #aboutMozilla::before in markup
[Actual Results]
Edit box does not close automatically.
[Expected Results]
Edit box closes automatically when switching to other elements.
Updated•8 years ago
|
Updated•8 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•8 years ago
|
||
This is a general focus issue, that does not only occur with the width/height fields of the box-model. So I don't think it should block bug 1150496.
You can try this other test case for example:
- select the #aboutMozilla node
- in the rule-view, click inside the "Filter Styles" input
- select the ::before pseudoelement in the markup
--> The focus remains inside the search input.
This does *not* happen with other node types however. If you select a non-pseudoelement in the markup, the focus goes to that element. So this is most probably an issue of the markup-view that does not acquire focus when a pseudo-element is selected.
Also, this happens in older versions of Firefox too. So I don't think it should block bug 1347964 either.
Assignee | ||
Updated•8 years ago
|
Summary: Edit box of box model does not close automatically when switching to ::before pseudo element → In put fields do not blur automatically when selecting a ::before pseudo element in the markup-view
Comment hidden (mozreview-request) |
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → pbrosset
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•8 years ago
|
||
Comment on attachment 8861399 [details]
Bug 1352776 - Make ReadOnlyEditor in the inspector also tabbable like other editors;
Hi Yura, I think you had worked on the tabindex logic of the markup-view. Do you mind taking a quick look and telling me if that's OK to do?
I think it should be. I'm essentially just making DOCTYPE and ::before/::after nodes in the markup-view tabbable, so they also acquire focus when selected, just like other nodes.
Attachment #8861399 -
Flags: feedback?(yzenevich)
Assignee | ||
Comment 4•8 years ago
|
||
Comment on attachment 8861399 [details]
Bug 1352776 - Make ReadOnlyEditor in the inspector also tabbable like other editors;
Let's get a review in parallel.
Attachment #8861399 -
Flags: review?(zer0)
Comment 5•8 years ago
|
||
Comment on attachment 8861399 [details]
Bug 1352776 - Make ReadOnlyEditor in the inspector also tabbable like other editors;
I believe it is, I initially was just duplicating the non-keyboard behavior, so as long as everything is consistent it looks good.
Attachment #8861399 -
Flags: feedback?(yzenevich) → feedback+
Comment 6•8 years ago
|
||
mozreview-review |
Comment on attachment 8861399 [details]
Bug 1352776 - Make ReadOnlyEditor in the inspector also tabbable like other editors;
https://reviewboard.mozilla.org/r/133390/#review138430
Stealing this quick review :) !
LGTM, just a comment nit.
::: devtools/client/inspector/markup/views/read-only-editor.js:27
(Diff revision 1)
> this.tag.textContent = node.doctypeString;
> } else {
> this.tag.textContent = node.nodeName;
> }
> +
> + // Make the "tag" part of this editor tabbable so it gets focused when selected.
nit: -1 means the element is focusable but not through keyboard navigation so "tabbable" seems incorrect here.
Attachment #8861399 -
Flags: review+
Comment hidden (mozreview-request) |
Pushed by pbrosset@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/21ea46a299d5
Make ReadOnlyEditor in the inspector also tabbable like other editors; r=jdescottes
Comment 9•8 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•