Thanx Sven,

This works great. Finally the site looks ok in Chrome, IE9, Opera and Firefox.

Hi,

this issue will be fixed with the next theme update. The last two chrome updates brought a different behavior of handling the SVGs.
If you want to fix it on your own, you can do the following:

Open images/dropdown.svg and images/top-a.svg in a TEXT/HTML Editor.

Both have a line of ode similar to the following:

<svg version="1.1" id="layer1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"  
     width="200px" height="100px" viewBox="0 0 200 100" enable-background="new 0 0 200 100" xml:space="preserve">

simply add preserveAspectRatio="none" to that code. It would then look like this:

<svg version="1.1" id="layer1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"  
     width="200px" height="100px" viewBox="0 0 200 100" enable-background="new 0 0 200 100" preserveAspectRatio="none" xml:space="preserve">

Regards
Sven

Hi,
I tried to use 'cover' here:

old version

#block-top-a > div > div {  
background: #1e1e1e url(../images/top-a.svg) 0 0 repeat;  
background-size: 100% 100%;  
}

new version:

#block-top-a > div > div {  
background: #1e1e1e url(../images/top-a.svg) 0 0 repeat;  
background-size:cover;  
}

and it works !!

Massimo

Updated chrome to "18.0.1025.142" and also updated Quantum j25 to "1.0.13" but the problem is still there.

I tried the work around but noticed that it helps with Chrome but then the menu is wrong in Opera. I can't test with IE9 because I'm still working with XP locally. Firefox is fine with and without work around.

So please YOOTHEME, what are your thought's about this? You said it's a bug in Google Chrome, now two updates later this is still there. This isn't good for you also, seeing that your demo site is also affected.

Can you make a better work around? So that it is ok for all latest browsers?
Is there a know timeframe when this will be adressed by Google?
Does Google actually know there is a bug in Chrome?

Pls YOOTHEME, what is your input?

It does work!!!

All in styles.css

lines 78 and 146

Thanks Massimo!

The same problem here, any work arounds on this one?

Just updated Chrome to 17.0.963.78 and the bug is still there

I have the exact same problem. How can we fix this?

Hi Artur,

Thanks for this info. Has Yootheme by chance reported this bug? I tried to report it and got a response, but they asked for clarification and I do not understand this bug well enough to explain. I see this issue on the demo of Quantum as well. Is it affecting any other templates that you know of?

Chrome users account for apprx 37%. I hate to have to wait a long period of time for the next Chrome release that will fix this. There have been bug updates released as recent as yesterday. Should I consider switching templates?

Any insight is appreciated.

Thanks!

hi,

this is a svg bug in the latest chrome release, which should be fix in the next chrome release.

greets,
artur