Closed
Bug 1349824
Opened 8 years ago
Closed 8 years ago
SVG element z-order incorrect when using group elements
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1141098
People
(Reporter: cedric, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [parity-Chrome][parity-Edge])
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36
Steps to reproduce:
If you define elements in an inline svg in a certain order the elements should be rendered in exactly that order. This works in normal cases. It should work as well if these elements are inside a group element.
Actual results:
However if these elements are enclosed in a group element the z-index order seems to be messed up.
An example of this can be observed here: https://jsfiddle.net/hm9n9pgb/
(In case you don't observe the same behaviour this is a screenshot of Firefox with my setup: https://own.arrakiz.org/index.php/s/gn6XvLpUOSWLzyT )
Expected results:
The order of the elements should be the same no matter if they are enclosed in a group or not. View the above jsFiddle in Google Chrome and you will see that Chrome renders both cases identical.
(Again, here is a screenshot in Chrome: https://own.arrakiz.org/index.php/s/GvQIQ4GDFgPzU6S )
Updated•8 years ago
|
Product: Firefox → Core
Comment 1•8 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=a799b5bff84c&tochange=b077c43a4306
Regressed by:
b077c43a4306 Jonathan Watt — Bug 776054 - Flip the prefs to enable the use of display lists for SVG painting and hit-testing. r=roc.
Blocks: 776054
status-firefox52:
--- → wontfix
status-firefox53:
--- → fix-optional
status-firefox54:
--- → fix-optional
status-firefox55:
--- → affected
status-firefox-esr45:
--- → wontfix
status-firefox-esr52:
--- → affected
Component: Untriaged → SVG
Keywords: regression
OS: Unspecified → All
Whiteboard: [parity-Chrome][parity-Edge]
Version: 52 Branch → 17 Branch
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•8 years ago
|
||
duplicate of bug 1141098, no?
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox52:
wontfix → ---
status-firefox53:
fix-optional → ---
status-firefox54:
fix-optional → ---
status-firefox55:
affected → ---
status-firefox-esr45:
wontfix → ---
status-firefox-esr52:
affected → ---
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•