Closed Bug 1420380 Opened 7 years ago Closed 7 years ago

referenced elements in SVG are behaving as if they are outside of the svg

Categories

(Core :: SVG, defect)

57 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: info, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171112125346

Steps to reproduce:

Added attribute vector-effect:non-scaling-stroke to all elements inside the svg. (This should make sure that the stroke-width does not scale with the svg)
And added mouseover and mouseout events to referenced elements. This should check if the element is inside the svg.

fiddle: http://jsfiddle.net/amberjs/crybr9aq/ 


Actual results:

The non-scaling-stroke attribute is ignored on referenced elements.
The referenced elements are considered to be outside the svg when they are inside when it is checked with event.originalTarget (mouseout) or event.relatedTarget (mousout)

fiddle: http://jsfiddle.net/amberjs/crybr9aq/ 


Expected results:

When the element that is given back in event.originalTarget or event.relatedTarget  is inside the svg, it should return true when checked with: svg.contains(element).

If an attribute is set on all elements in the svg, it should also apply to the referenced elements.

fiddle: http://jsfiddle.net/amberjs/crybr9aq/
We're need to have only one issue per bug. It might be best to close this and then raise the two issues as separate bugs.
Flags: needinfo?(info)
Issue 1 is invalid per the SVG 2 specification.
Component: Untriaged → SVG
Product: Firefox → Core
Perhaps you could explain why (with reference to the appropriate w3c specifications) you've come to the conclusions you have about relatedTarget and originalTarget
Raised the issues as separate bugs as requested: 
https://bugzilla.mozilla.org/show_bug.cgi?id=1420851
https://bugzilla.mozilla.org/show_bug.cgi?id=1420848
Flags: needinfo?(info)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.