STR:
1. Visit this data URL:
```
data:text/html,<i>Ital</i>TryToFocusMeInInspector
```
2. Open Inspector (F12) and click the "Fonts" pane on the right side.
3. Try to focus the "TryToFocusMeInInspector" text in the left pane.
ACTUAL RESULTS:
When you attempt to focus the raw text ("TryToFocusMeInInspector"), then the `<body>` node ends up being focused instead. (In other words, we refuse to focus the text.)
EXPECTED RESULTS:
I should be able to focus the raw text.
Note: I get EXPECTED RESULTS if I have another pane focused on the right side (e.g. Layout or Computed or Changes). If I've got the text focused and then I switch from something else to the fonts pane, then the focus immediately resets to to the body node.
In practice, this is really annoying in scenarios where you're trying to navigate through the DOM in inspector by pressing "downarrow" over and over to skip over uninteresting nodes. If you happen to run across a node that trips this bug, then you won't ever be able to inspect past it (not by using downarrow, at least), because we skip back to the body each time you reach the text node. And it's non-obvious in practice what's causing this (the font pane being focused), so when this happens, it just feels like devtools are entirely broken.
mozregression says this started happening when bug 1485324 landed (enabling the new Font Editor) -- the old/simpler Fonts pane didn't have this problem.
Bug 1526054 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
STR:
1. Visit this data URL:
```
data:text/html,<i>Ital</i>TryToFocusMeInInspector
```
2. Open Inspector (F12) and click the "Fonts" pane on the right side.
3. Try to focus the "TryToFocusMeInInspector" text in the left pane.
ACTUAL RESULTS:
When you attempt to focus the raw text ("TryToFocusMeInInspector"), then the `<body>` node ends up being focused instead. (In other words, we refuse to focus the text.)
EXPECTED RESULTS:
I should be able to focus the raw text. (Bonus points if the Fonts pane shows something useful for it. :) Presumably I can't directly restyle the text node since there's no style attribute, but the pane could at least tell me what font is being used for the text.)
Note: I get EXPECTED RESULTS (i.e. I can focus the text node) if I have a different pane focused on the right side -- something **other** than the Font Editor. (e.g. the Layout or Computed or Changes pane). Though, if I've got the text focused and then I switch from something else to the Font Editor pane, then the focus immediately resets to to the `<body>` node.
In practice, this is really annoying in scenarios where you're trying to navigate through the DOM in inspector by pressing "downarrow" over and over to skip over uninteresting nodes. If you happen to run across a node that trips this bug, then you won't ever be able to inspect past it (not by using downarrow, at least), because we skip back to the body each time you reach the text node. And it's non-obvious in practice what's causing this (the font pane being focused), so when this happens, it just feels like devtools are entirely broken.
mozregression says this started happening when bug 1485324 landed (enabling the new Font Editor) -- the old/simpler Fonts pane didn't have this problem.