Closed
Bug 1196748
Opened 9 years ago
Closed 9 years ago
Bug with SVG and classes
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 265894
People
(Reporter: m+mozilla, Unassigned)
Details
Attachments
(1 file)
16.48 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20150819030206 Steps to reproduce: http://jsbin.com/piriqequvo/1/edit?html,output Expected results: It should display the SVG. It works on Chrome.
As you can see in the attachment, my selectors work but it doesn't render well. Plus, if you tick the display:none off, it works.
Comment 3•9 years ago
|
||
The svg within the pmd-Thumbnail-action is display none per .pmd-Thumbnail-action svg { display: none; } So nothing should be rendered, which is what Firefox does. Why do you think it should be otherwise?
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Did you see my attachment? Plus it's not the "action" which is display:none but its svg.
Sorry I misread your comment but still. See my attachment. And it works on chrome.
Comment hidden (obsolete) |
Comment hidden (obsolete) |
(In reply to Robert Longson from comment #3) > The svg within the pmd-Thumbnail-action is display none per > > .pmd-Thumbnail-action svg { > display: none; > } > > So nothing should be rendered, which is what Firefox does. Why do you think > it should be otherwise? Because there's more specific selector over there. I figured out that it's inner SVG in anonymous content what's causing it. So inner SVG gets "display:none" due to the selector. Fixing the selector to ".pmd-Thumbnail-action > svg" (adding ">") fixes it. Robert, do you think it should work like that? http://ss.ssmaker.ru/d4ffc531.png
Flags: needinfo?(longsonr)
Comment 10•9 years ago
|
||
Here's example without [data-type] http://jsbin.com/tuximilala/1/edit?html,output
Reporter | ||
Comment 11•9 years ago
|
||
In fact, it's probably that. In the inspector, you do not see that "use" uses another svg, so you think there's only one svg tag but nope.
Comment 12•9 years ago
|
||
Ahh, I see what's going on now. The data-type was a red-herring, sorry about that. When we clone the <use> svg into the document it basically becomes another <svg> within that document and we then erroneously keep it as display: none as the other selector (the one in comment 1) matches it. So it is a valid bug after all, although we do know about it.
Flags: needinfo?(longsonr)
Resolution: INVALID → DUPLICATE
Reporter | ||
Comment 13•9 years ago
|
||
Thank you very much. ;)
You need to log in
before you can comment on or make changes to this bug.
Description
•