Bug 120903 - ASSERTION FAILED: mode & UseTransforms with a fixed-position <svg>
Summary: ASSERTION FAILED: mode & UseTransforms with a fixed-position <svg>
Status: RESOLVED DUPLICATE of bug 31278
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
: 117925 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-09-06 15:48 PDT by Vicki Pfau
Modified: 2017-02-08 10:30 PST (History)
6 users (show)

See Also:

Attachments
Repro (36 bytes, text/html)
2013-09-06 15:48 PDT, Vicki Pfau 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vicki Pfau 2013-09-06 15:48:11 PDT 
Created attachment 210807 [details]
Repro

An SVG element with position: fixed will trigger an assertion (mode & UseTransforms) in RenderSVGRoot::mapLocalToContainer(const WebCore::RenderLayerModelObject *, WebCore::TransformState &, MapCoordinatesFlags, bool *) const when running a debug build. A simple repro is attached.

<rdar://problem/14703176>
Comment 1 Tim Horton 2013-09-06 16:05:37 PDT 
IIRC we (Simon and I) decided that the assertion didn’t actually make any sense, but I don’t remember all the logic at the moment.
Comment 2 Dirk Schulze 2013-09-07 01:18:17 PDT 
(In reply to comment #1)
> IIRC we (Simon and I) decided that the assertion didn’t actually make any sense, but I don’t remember all the logic at the moment.

Hm, I agree. It makes sense for inner SVG elements but not for outer SVG elements (SVGRoot is always the outer SVG element). Looks like the assertion is wrong here.

Just a question for understanding. The comment assumes that the mode (isFixed) comes from the content. I would assume that the mode is from the current renderer. Which is true? If it is the latter, we can remove the assertion.
Comment 3 Vicki Pfau 2013-10-08 13:22:40 PDT 
*** Bug 117925 has been marked as a duplicate of this bug. ***
Comment 4 Said Abou-Hallawa 2017-02-08 10:30:27 PST 

*** This bug has been marked as a duplicate of bug 31278 ***