A height: 100vh element makes add-on options_ui page continuously growing
Categories
(Toolkit :: Add-ons Manager, defect, P3)
Tracking
()
People
(Reporter: manikulin, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0
Steps to reproduce:
I was debugging conditions causing the Bug #1774722 when I got a surprising dynamic effect on the add-on preferences page.
- Load the add-on provided below as a temporary extension
- Open add-on management tab, choose the just loaded extension, switch to its preferences
- Try to open the
<details>element - Watch at the scrollbar, try to scroll to the bottom of the page
manifest.json
{
"manifest_version": 2,
"name": "bug-growing-options",
"version": "0.1",
"options_ui": { "page": "bug-growing-options.html" }
}
bug-growing-options.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Growing scrollbar</title>
</head>
<body>
<h1>Growing scrollbar</h1>
<details>
<summary>Open this, but be prepared to close it again</summary>
<div style="height: 100vh; background: gray;">Content causing overflow.</div>
</details>
</body>
</html>
Actual results:
- Animation of growing page, size of the scroller is becoming smaller for some time
- Page is becoming higher on attempt to scroll to bottom using mouse (see the Bug #1770726 for scrolling from keyboard)
Expected results:
The block element having its height in vh is rendered to fixed size even on add-on preferences page.
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•2 years ago
|
||
Hello,
I reproduced the issue on the latest Nightly (103.0a1/20220619215938), Beta (102.0b9/20220616185542) and Release (101.0.1/20220608170832) under Windows 10 x64 and Ubuntu 16.04 LTS.
The issue occurs as mentioned in the “Actual results” section of Comment 0 when using the attached extension.
|
||
Comment 3•2 years ago
|
||
I recalled we had another bug filed for this same issue in the past, and so I looked for the duplicate.
That bug was Bug 1610227, which is marked as fixed, and so it seems that we may have reintroduced or 100vh is another way to trigger the same and the original change didn't completely fix the issue.
I'm still linking the old bug report as a seealso and I'm assigning a needinfo to myself as a reminder to look into this.
|
|
||
Updated•2 years ago
|
Description
•