1410611 - CSS style not applied to SVG <use> element referencing external file

Status: RESOLVED DUPLICATE of bug 619632

(Core :: SVG, defect)

Description

[Tim Pederick]

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

Steps to reproduce:

1. Create an SVG file that defines a graphical object. Style said object using CSS in the same file.
2. Create an SVG file (or HTML file using SVG) with a <use> element referencing the file from step 1.

Test cases are provided at the following location:
https://gist.github.com/perey/4512b9a060a61320c36f9daa90bf82cb


Actual results:

The graphical object will be rendered using the default style.


Expected results:

The graphical object should be rendered using the CSS-specified style.

This is a regression; it was behaving as expected at least as recently as April 2017.

Comment 1

[Robert Longson [:longsonr]]

Seems like a duplicate of bug 619632 which has never worked.

Comment 2

[Tim Pederick]

I promise you this was working as recently as 27 April 2017. That's the date of the git commit on the file that I went back to today and suddenly found all the SVGs blacked out.

Comment 3

[Robert Longson [:longsonr]]

Displays just the same in a Firefox nightly from January 2016.

Comment 4

[Tim Pederick]

Hmm. You're right. My minimal test case was too minimal; it looks like the actual problem is something else. There's also CSS that applies in the HTML file. (My next guess was that it doesn't recognise the class attribute on the element that <use> references... but no, doing that works fine in both old and new versions.)

It looks like I'm going to have to give up on reducing it to a test case and just post the code that's giving me the problem. Would the appropriate action be to edit this bug, or to file a new one?

Comment 5

[Robert Longson [:longsonr]]

A new bug would likely be less confusing as we can't edit any previous comments.

Note that Firefox has recently changed to implement SVG 2 rules for use elements which are different to SVG 1.1 rules so your new testcase may well be invalid too because we're not going to go back to what we had before which was neither SVG 1.1, nor SVG 2 compliant. We do expect the other browsers to implement SVG 2 <use> at some point. See bug 1406418 for an example.