Opening about:support with an URL fragment does not scroll to selected section
Categories
(Toolkit :: General, defect, P5)
Tracking
()
People
(Reporter: phd, Assigned: gliu10000, Mentored)
References
Details
Attachments
(1 file)
Steps to reproduce:
Open "about:support" with an URL fragment, like:
about:support#place-database
Actual results:
"about:support" page is scrolled to top, and does not scroll to selected section (h2 tag).
You need to focus address bar (F6) and confirm the URL again (Return) for it to scroll to the given section.
Expected results:
"about:support" with an URL fragment should be opened already scrolled to selected section.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Panning and Zooming' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•2 years ago
|
||
I expect it's a result of the page being populated asynchronously after the load
event. It'd have to be populated sooner, and even then the async-ness might mean it won't work (or be unreliable). Alternatively, we'd have to manually check for the hash on pageload in aboutSupport.js and force the scroll that way.
Comment 3•2 years ago
|
||
Hello,
I reproduced the issue as per the mentioned STR on the latest Nightly (98.0a1/20220131212843), Beta (97.0/20220131171509) and Release (96.0.3/20220126154723) under Windows 10 x64 and Ubuntu 16.04 LTS.
Pasting “about:support#place-database” in the address bar and hitting Return will open the about:support page scrolled at the top and not at he selected section, as described in the report.
After the above, focusing the address bar and hitting Return again will indeed scroll to the given section.
Updated•2 years ago
|
Hey there! I'd be happy to upload a fix for this.
Alternatively, we'd have to manually check for the hash on pageload in aboutSupport.js and force the scroll that way.
It seems like your assumption is correct. I did some testing with some code that forces a scroll on page load, and that seemed to resolve the issue.
If this is something we're planning on implementing, I can send over a patch for review.
Comment 5•2 years ago
|
||
(In reply to gliu20 from comment #4)
Hey there! I'd be happy to upload a fix for this.
Alternatively, we'd have to manually check for the hash on pageload in aboutSupport.js and force the scroll that way.
It seems like your assumption is correct. I did some testing with some code that forces a scroll on page load, and that seemed to resolve the issue.If this is something we're planning on implementing, I can send over a patch for review.
Sure, I would be happy to take a patch for this.
Updated•2 years ago
|
Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/autoland/rev/13e44c376f15 Scroll to hash on pageload in about:support. r=Gijs
Comment 8•2 years ago
|
||
bugherder |
Comment 9•2 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 10•2 years ago
|
||
Verified the fix on the latest Nightly (100.0a1/20220322214632) under Windows 10 x64 and Ubuntu 16.04 LTS.
Following the original STR, pasting “about:support#place-database” in the address bar and hitting Return will now open the about:support page scrolled at the correct section (Places Database), confirming the fix.
Description
•