Closed
Bug 1258571
Opened 9 years ago
Closed 9 months ago
Markup doesn't display anything after using "Search HTML" on different pages in tab history
Categories
(DevTools :: Inspector, defect, P2)
DevTools
Inspector
Tracking
(firefox48 affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox48 | --- | affected |
People
(Reporter: arni2033, Unassigned)
References
Details
(Whiteboard: [btpp-fix-later])
>>> My Info: Win7_64, Nightly 48, 32bit, ID 20160320030409
STR:
1. Open the following "data:" url in a new tab
data:text/html,<div class="b_element"><span class="no_element">before</span></div><style>.b_element::before{content:"_span_"}
2. Paste the following "data:" url into urlbar in the tab from Step 1 and press Enter
data:text/html,<div class="b_element"><span class="no_element"></span></div><style>.b_element::before{content:"_span_"}
3. Open inspector, type "element" in the field "Search HTML"
4. Press Enter 3 times (with pauses ~2s just in case)
5. Press Alt+Left to go back in the tab history (-1)
[make sure that "Search HTML" field is still focused and has the same value - "element"]
6. Press Enter 3 times (with pauses ~2s just in case)
7. Press Alt+Right to go forth in tab history (+1)
AR:
In Step 4 switching works fine. Markup is OK
In Step 5 markup is shown OK
In Step 6 after the 1st pressing no elements are selected. Counter still displays "3 of 3"
after the 2nd-3rd pressings no elements are selected, counter says "2 of 3", "3 of 3"
In Step 7 makup is blank
ER:
In Step 6 "Search HTML" should switch to elements and update the counter correctly
In Step 7 markup should be shown
Note:
1) Looks like I can't reproduce it with searching with selectors, even if I use selector for exactly
those 3 nodes. So presumably this is specific to "Search text" feature (implemented in bug 835896)
2) Firefox DevEdition 45 (ID 20151222004010) is affected
Comment 1•9 years ago
|
||
This is most likely due to the way the page is restored from the bfcache. I'm guessing that the search is still being done on the previous page. There is an error in the console when searching after going back:
Protocol error (unknownError): TypeError: node.defaultView is null
inspector-search.js:63
Priority: -- → P2
Whiteboard: [btpp-fix-later]
Not reproducible on the last build before bug 835896. Reproducible on the 1st build after bug 835896.
First bad 437545b472e74a71ca112f4b4a300ae0a646288b (fx-team)
Last good f00a24682d57e48a287e11bcfc72e562929fd007 (mozilla-inbound)
Also good 43f23a377c8510f29aa9546453b3b3bcb7810b07 (fx-team)
> regression-range 1 (mozilla-inbound) https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f00a24682d57e48a287e11bcfc72e562929fd007&tochange=961911623a6f2ec1d036c7b12a5117ebbeff45d8
> regression-range 2 (fx-team) https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=43f23a377c8510f29aa9546453b3b3bcb7810b07&tochange=437545b472e74a71ca112f4b4a300ae0a646288b
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•3 years ago
|
Severity: normal → S3
Comment 3•9 months ago
|
||
works fine for me now. Might be related to all the work around fission/EFT
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•