getBoundingClientRect returns the wrong size for fixed position SVG content since bug 1340715
Categories
(Core :: SVG, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox107 | --- | wontfix |
firefox108 | --- | wontfix |
firefox109 | --- | wontfix |
firefox110 | --- | fixed |
People
(Reporter: birtles, Assigned: TYLin)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files, 1 obsolete file)
See the attached test case. In Chrome and previous versions of Firefox this produced a bounding box 300px wide but in recent versions of Firefox the bounding box has zero width.
Mozregression points to bug 1340715.
Reporter | ||
Comment 1•2 years ago
|
||
Even without running the JS, you can see that the bbox has zero width when you highlight <div id=div>
in the DevTools.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1340715
:TYLin, since you are the author of the regressor, bug 1340715, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Re comment 0:
See the attached test case. In Chrome and previous versions of Firefox this produced a bounding box 300px wide but in recent versions of Firefox the bounding box has zero width.
Yes, Chrome 110 produces a bounding box of 300px width, but any Firefox version before bug 1340715 produces a bounding box of the current window width.
Reporter | ||
Comment 4•2 years ago
|
||
300px still seems preferable to 0px as (a) it would match Chrome and (b) wouldn't confuse code trying to detect hidden elements.
Assignee | ||
Comment 5•2 years ago
|
||
To match blink and webkit's behavior.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 8•2 years ago
|
||
bugherder |
Comment 10•2 years ago
|
||
The patch landed in nightly and beta is affected.
:TYLin, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox109
towontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 12•2 years ago
|
||
This bug fixed a regression. The patch in the original bug is too risky for a uplift, so does this patch.
Assignee | ||
Comment 13•2 years ago
|
||
This makes Firefox behave like Google Chrome.
Comment 14•2 years ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
Comment 16•2 years ago
|
||
Comment on attachment 9317550 [details]
Bug 1801581 - Make preferred isize of SVG with fit-content value fall back to fallback intrinsic size. r?#firefox-svg-reviewers
Revision D169778 was moved to bug 1811683. Setting attachment 9317550 [details] to obsolete.
Assignee | ||
Comment 17•2 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #15)
Yeah, wrong bug?
Oops, the patch is for bug 1811683.
Description
•