1770110 - Page jumps to the beginning after used developer tool Inspector and reload

Status: NEW

(DevTools :: General, defect, P3)

Description

[mike]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:101.0) Gecko/20100101 Firefox/101.0

Steps to reproduce:

The developer tools are open and I have scrolled the page down. Now I make a selection with the inspector on a html element and reload (e.g., F5) the page.

Actual results:

The page jumps back to the beginning and I have to scroll back to the location I checked before. When the developer tools are closed the jump does not happen.

Expected results:

Scrolling down again and again is very annoying during development. Better if the page stands at this point even if I make a reload.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Julian Descottes [:jdescottes]]

Would be great to get regression window.
STRs:

• open https://bugzilla.mozilla.org/show_bug.cgi?id=1770110
• open devtools > inspector
• select a node in the markup view
• scroll content page to bottom
• reload

ER: Scroll should stick to bottom after reload
AR: Scroll is reset to top

Comment 3

[Catalin Sasca, Desktop Test Engineering [:csasca]]

Found the regression between 2021-08-16 and 2021-08-17.

Mozregression pinpointed to :
Bug 1702715 - [devtools] Enable server side target switching. r=bomsy,Honza,jdescottes,ladybenko.

build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/R5cjI2hETq-kFqMFS7g2_A/runs/0/artifacts/public%2Fbuild%2Ftarget.dmg
changeset: 556581f9b280231c5d9bcd0df3de0870e4e23d67
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=556581f9b280231c5d9bcd0df3de0870e4e23d67&tochange=62ee94c26f8f0e526f2d381b6c5ef50effef20ff

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

:csasca, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit auto_nag documentation.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

:nchevobbe, since you are the author of the regressor, bug 1702715, could you take a look?
For more information, please visit auto_nag documentation.

Comment 6

[Julian Descottes [:jdescottes]]

Thanks a lot for the regression window!
Since this bug was a preference flip, it's going to be difficult to find the cause just based on this, clearing the ni for now.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1702715

Comment 8

[Donal Meehan [:dmeehan]]

Is this something we can address in an upcoming release?

Comment 9

[Ryan VanderMeulen [:RyanVM]]

Can you please run mozregression again with the pref flipped to true to help find a more suitable regression range?

Comment 10

[Catalin Sasca, Desktop Test Engineering [:csasca]]

Sure thing, redid the regression with the pref set to true, and I got between 2021-05-12 and 2021-05-13. Unfortunately, mozregression will skip all the builds between and not continue the bisection.

Here is the pushlog for 2021-05-13, hope it helps: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=95d93c007301f5a90edf1e8f79641f7c7569ba68&tochange=940a3ad12e3dc9b2809b02f6a8ac8e941a50d2a1

Comment 11

[Ryan VanderMeulen [:RyanVM]]

Julian, I see a few different devtools-related changes in that range - do any of those look plausible to you?

Comment 12

[Julian Descottes [:jdescottes]]

(In reply to Donal Meehan [:dmeehan] from comment #8)

Is this something we can address in an upcoming release?

Bug is triaged as P3 / S3, doesn't have to be fixed urgently. Will take a look at the pushlog provided