Closed Bug 1950367 Opened 1 year ago Closed 1 year ago

after switching from Inspector to another devtools tab and back, on some pages, the scroll position is reset

Categories

(DevTools :: Inspector, defect)

Firefox 136
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1946690

People

(Reporter: jaborandi, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:136.0) Gecko/20100101 Firefox/136.0

Steps to reproduce:

  1. go to google.com
  2. right-click the magnifier icon in the search bar and click Inspect
  3. switch to Console tab
  4. switch back to Inspector tab

Actual results:

on step 4 html inspector is scrolled to the top, with selected (highlighted with blue) element down behind the visible area

Expected results:

scroll position in Inspector should have remained unchanged

note: the bug is intermittent, at some point it Inspector may suddenly start maintaining the scroll position, if this happens - reload the page and try again

first i thought that modification of the DOM triggers this, but i tried doing it on a simple page without this bug - and it still doesn't have it

Summary: after switching from Inspector to another devtools tab and back, in case of a sufficiently big code, the scroll position is reset → after switching from Inspector to another devtools tab and back, on some pages, the scroll position is reset

The Bugbug bot thinks this bug should belong to the 'DevTools::Inspector' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Inspector
Product: Firefox → DevTools

Thanks jaborandi for the report.
This looks a lot like Bug 1946690 , which was fixed in Firefox 137.
Could you try your case on Nightly and check it's fixed?
Thanks

Flags: needinfo?(support)

:nchevobbe yes, it seems to be fixed in 137
thank you!

Flags: needinfo?(support)

Great! Let's close this bug then

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1946690
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.