webp not displaying border img in chrome mobile 39.0.2

[me6...@gmail.com]

Chrome mobile v 30.0.2 doesn't display border image with webp files?
Eg. Www.graystflowers.com.au

[me6...@gmail.com]

Have since figured out it's not chrome mobile exactly, but the reduce data usage option, turn that off and it works fine, don't ask me why, if I can find a way to detect if the border doesn't work I'll just default it back to jpeg, which I'm doing in non supportive browsers anyway.

[Pascal Massimino]

Hi,

On Wed, Dec 17, 2014 at 12:25 PM, <me6...@gmail.com> wrote:

Have since figured out it's not chrome mobile exactly, but the reduce data usage option, turn that off and it works fine, don't ask me why, if I can find a way to detect if the border doesn't work I'll just default it back to jpeg, which I'm doing in non supportive browsers anyway.

Did you mean: reduce data usage option didn't not convert your JPEG to WebP? Or was the image totally broken (for some reasons)?

Do you have the exact URL of the image concerned? 

For instance, i see this one is in  WebP format: http://www.graystflowers.com.au/images/420/corporate/webp/chrysanthemums_asiatic_lilies.jpg.webp

But i'm not sure this is the one you are referring to...

Thanks!

On Wednesday, December 17, 2014 8:39:56 PM UTC+11, me6...@gmail.com wrote:

Chrome mobile v 30.0.2 doesn't display border image with webp files?
Eg. Www.graystflowers.com.au

--
You received this message because you are subscribed to the Google Groups "WebP Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webp-discuss...@webmproject.org.
To post to this group, send email to webp-d...@webmproject.org.
Visit this group at http://groups.google.com/a/webmproject.org/group/webp-discuss/.
For more options, visit https://groups.google.com/a/webmproject.org/d/optout.

[me60732]

All the images on that site have 2 files,  one jpeg (for non supporting browsers) and a webp which sits in the webp folder. Step out of that folder (../) and you have the jpegs same file name minus the extension .webp.

The webp image displays fine but it is Supposed to have an image border.

Which works for jpegs (and webp but only with reduce data usage turned off)?

[Pascal Massimino]

On Wed, Dec 17, 2014 at 4:41 PM, me60732 <me6...@gmail.com> wrote:

All the images on that site have 2 files,  one jpeg (for non supporting browsers) and a webp which sits in the webp folder. Step out of that folder (../) and you have the jpegs same file name minus the extension .webp.

The webp image displays fine but it is Supposed to have an image border.

Which works for jpegs (and webp but only with reduce data usage turned off)?

Sorry, i can't reproduce here, with Android 5.0 and Chrome mobile 39.0.2171.93 

The border is fine in both cases.

Maybe you're on iOS?

Since the border is not 'burnt-in' in the images (cf: http://www.graystflowers.com.au/images/420/corporate/webp/chrysanthemums_asiatic_lilies.jpg.webp

and http://www.graystflowers.com.au/images/420/corporate/chrysanthemums_asiatic_lilies.jpg) it might be a problem with the animation/caption code...

[me6...@gmail.com]

Nice to know it doesn't happen on android 5, however i'm on 4.4.2.  The border image and transitions are applied with css, there not javascript, all the javascript does is randomise the images, pauses the slideshow if the next image hasn't loaded yet, changes the opacity for the current and next image, and set the opacity to 0 or 1 for the caption, the rest is all css. I could do the whole lot in css, however that wouldn't fail gracefully in older browsers, as is, older browsers (IE8) just don't get the transition effect, and depending on the browser, might just get a plain old css border, instead of a border image.

I was hoping it was something simple, I did only just discover webp yesterday, wasn't even what I was looking for at the time, so I was hoping it might have been the wrong mime type (image/webp) or something like that.  have used image/jpeg to, although doesn't seem right made no difference.

But I'll change my support detection function to detect if the image border exists, if not then it can default to jpegs, which works fine.

Don't have any problem with Opera, or desktop chrome.  and I figure it's only a matter of time before this format is widely supported, it's just like PNG's when they first came out.

On Wednesday, December 17, 2014 8:39:56 PM UTC+11, me6...@gmail.com wrote:

[James Zern]

Hi,

On Wednesday, December 17, 2014 4:22:07 PM UTC-8, me6...@gmail.com wrote:

Nice to know it doesn't happen on android 5, however i'm on 4.4.2.  The border image and transitions are applied with css, there not javascript, all the javascript does is randomise the images, pauses the slideshow if the next image hasn't loaded yet, changes the opacity for the current and next image, and set the opacity to 0 or 1 for the caption, the rest is all css. I could do the whole lot in css, however that wouldn't fail gracefully in older browsers, as is, older browsers (IE8) just don't get the transition effect, and depending on the browser, might just get a plain old css border, instead of a border image.

I was hoping it was something simple, I did only just discover webp yesterday, wasn't even what I was looking for at the time, so I was hoping it might have been the wrong mime type (image/webp) or something like that.  have used image/jpeg to, although doesn't seem right made no difference.

But I'll change my support detection function to detect if the image border exists, if not then it can default to jpegs, which works fine.

Don't have any problem with Opera, or desktop chrome.  and I figure it's only a matter of time before this format is widely supported, it's just like PNG's when they first came out.

If it's only a problem with the reduce data usage option set can you leave a page up that exhibits the problem? Maybe the people running the proxy can have a look.

[me6...@gmail.com]

work it out, google proxy is caching an older version of the css file where the border image isn't applied to the webp files.

On Wednesday, December 17, 2014 8:39:56 PM UTC+11, me6...@gmail.com wrote: