Support crossOrigin attribute on image and feImage elements

Assigned to



3 years ago
9 months ago


(Reporter: longsonr, Assigned: longsonr)


(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)



(1 attachment, 1 obsolete attachment)

Comment hidden (empty)


3 years ago
Assignee: nobody → longsonr

Comment 2

3 years ago
Cam, is the SVG specification right? It says 

attribute DOMString crossOrigin;

but the html DOM in gecko (and my WIP patch) has

attribute DOMString? crossOrigin;


3 years ago
Flags: needinfo?(cam)
Checking the HTML spec, it looks like it should indeed be "DOMString?".  I've updated the spec:
Flags: needinfo?(cam)
(In fact the HTML spec changed underneath us.)

Comment 5

3 years ago
Created attachment 8709662 [details] [diff] [review]
working patch
Attachment #8708824 - Attachment is obsolete: true

Comment 6

3 years ago
This seems to work but I don't know how to write an automated test for it. Any suggestions?
Flags: needinfo?(dholbert)
I imagine the tricky part of the automated test is the cross-origin part, right?
That's explained a bit here:

I'd expect you want to write a mochitest which...
 * ...uses SVG in an iframe and snapshotWindow to see whether stuff rendered or not, like this test:

 * ...uses an <image> & <feImage> that point to '', which the mochitest web server will recognize and map to your source tree, like in these tests:

A few other thoughts:
 * Promises make the iframe load callbacks a bit easier to follow.  If you're not too familiar with promises, feel free to crib from my test_use_with_hsts.html test and ping me with questions. Or, traditional async callbacks shouldn't be too complex either.
 * For robustness, your SVG file (or SVG files) should include both elements (<feImage> & <image>), with the crossOrigin attribute present & not-present.
Flags: needinfo?(dholbert)
Blocks: 1328534
You need to log in before you can comment on or make changes to this bug.