1191437 - The mute icon flashes the first time that you click on it on a window

Status: REOPENED

(Core :: SVG, defect)

Description

[(no longer active)]

Markus tells me that we need to use an image stripe to work around this.

Comment 1

[Markus Stange [:mstange]]

"sprite"

At least that's how we usually work around this problem. Though sometimes we use some other trick to preload the other image states, for example setting it as an offscreen background image somewhere.

Comment 2

[Stephen Horlander [:shorlander]]

(In reply to Markus Stange [:mstange] from comment #1)
> "sprite"
> 
> At least that's how we usually work around this problem. Though sometimes we
> use some other trick to preload the other image states, for example setting
> it as an offscreen background image somewhere.

I can make it a sprite, although that does remove the benefit of referencing individual elements in the SVG file.

I thought we would have to load the whole SVG file once it was referenced. Guess we only load the referenced sections?

Comment 3

[Markus Stange [:mstange]]

Oh cool, I didn't know that was how it's working. I don't know what we do for SVG sections, but it seems like the flash is unnecessary then, and it would be worth filing a bug about it.

Comment 4

[(no longer active)]

The muted icon is tab-audio.svg#tab-audio-muted as opposed to the normal icon (tab-audio.svg#tab-audio) so I guess separate sections are loaded separately...

Comment 5

[Stephen Horlander [:shorlander]]

I wonder if it's just because of the <use>? Changing the markup might fix it… I will try it and see. If not I can still make it a sprite.

Comment 6

[(no longer active)]

Thanks!

Comment 7

[(no longer active)]

The new icons that shorlander provided did not fix this problem, so I had to modify them myself to make a sprite out of them, and with the sprite, this will be fixed in bug 1192568.

Comment 8

[Dão Gottwald [:dao]]

We really shouldn't have to work around this like that. IDs are much easier to maintain than image regions.

Comment 9

[Dão Gottwald [:dao]]

Also adding Robert Longson and dholbert who seem to have worked on SVG more recently...?

Comment 10

[(no longer active)]

We are not going to block on a platform bug fix at this point.

Comment 11

[Markus Stange [:mstange]]

Seth, do you know what's causing this?

Comment 12

[Seth Fowler [:seth] [:s2h]]

(In reply to Markus Stange [:mstange] from comment #11)
> Seth, do you know what's causing this?

Yeah, I suspect I do. The symptoms above didn't make sense to me, given that we're talking about an SVG here, until I realized that this is yet another problem caused by #-moz-samplesize and #-moz-resolution, which force us to use a separate image cache entry for an image whenever the fragment identifier changes, causing us to actually have to load a second (or third, or fourth...) copy of the image.

Tell me if you've heard this one before: this will be fixed as part of downscale-during-decode. Fortunately we are getting really close now. -moz-samplesize can already be removed, and -moz-resolution should become removable during this cycle.

Clearing jwatt's needinfo since I think we have this diagnosed.

Comment 13

[arni2033]

I encounter the same bug with many SVG icons (when I hover them the 1st time in session):
0) Sound indicator (this bug)
1) "New add-on" button in urlbar (actually I think that some other urlbar buttons are affected)
2) Active "back", "forward", "reload", "bookmark" icons in context menu
CCing this bug to check if (1), (2) will be fixed as well.