New WebP Support

[Rob-Xar]

Rob, thank you for advising. Your logic is unclear. When will the fall-back kick in? Is it for my browser or the end viewer?
I work with a browser that supports WebP but when does your code detect the end viewer's browser cannot.

Clearly I am publishing a website that is supposed to be agnostic to the browser viewing it.

If I open your link in IE, I get:



All WebPs that do not render, no JPEGs, no fall-back.
I build sites for others; not to look at things in my cosy den.

Acorn

Hi Acorn,

IE is no longer supported, nor is it supported by Microsoft, it was dropped last year. We can log this but I don't think it would get any priority. I would suggest using a modern browser such as Chrome/Edge/FireFox etc

You can also turn the option off in Web Properties also if you really want to make sure it works in IE

[Acorn]

Hi Acorn,
IE is no longer supported, nor is it supported by Microsoft, it was dropped last year. We can log this but I don't think it would get any priority. I would suggest using a modern browser such as Chrome/Edge/FireFox etc
You can also turn the option off in Web Properties also if you really want to make sure it works in IE

I am not being obtuse here. Either the export presents WebP for WebP-aware browsers or its fall-back is to JPEG/PNG.

I am sorry I chose IE as a case study where your coding does not present JPEG/PNG.
It is the only browser I have that does not support WebP.
Your XDAs still use IE: "IE is no longer supported, nor is it supported by Microsoft, it was dropped last year."

I don't need IE covered, thank you.

What would have been useful was a proper explanation that the JPEG/PNG files are created and placed in the index_htm_files/ folder where a non-WebP browser will have Xara codes to point to these instead.

It eventually clicked and I looked in the manifest, xr_files.txt:

• index_htm_files/Fred.jpg - 9.4kB
• index_htm_files/Fred.webp - 3.65kB
• index_htm_files/Snowy_Tree.jpg - 126kB
• index_htm_files/Snowy_Tree.webp - 78.5kB
• index_htm_files/Snowy_Tree@2x.jpg - 485kB
• index_htm_files/Snowy_Tree@2x.webp - 302kB

I note you have already corrected your WebP File Format page.
I hope you alter the default for Include WebP images to off.
Your

Please note: This will increase the time it takes to export your website. If you check this option and republish, it will have to do a full publish again rather than quick publish.

Is it not the case that only if unticked and then ticked do you require a full publish (a first publish is always full). While ticked, updates can use quick publish thereafter?

I have corrected a statement in https://www.talkgraphics.com/showthr...216#post636216 but the rest of the observations still stand.
I will update my first Post to this Thread.

I followed @MB365's Posts with links to this Thread to show how OTT is was to target every past complaint over image formats in such a fashion.
Perhaps we would have a better understanding if you replied to each concern at the time and indicate that it has been added to the Backlog.
Ignoring TGer valid concerns for so long and then going Ta-Da is infra-dig.

Acorn

[Egg Bramhill]

Bit late on parade here...
Firstly I'd comment that the inclusion of webp is a great new feature, one members have been requesting a lot recently. So with this, hidef and fit to width I'd like to say that Xara is getting back on track over the past few months.

I can only test whether the new webp inclusion serves up non webp images as an alternative by testing it on my iphone6 which has an old version of Safari. Safari is the latest big browser to support webp but the version on my iphone isn't capable afaik. This browsers loads an image. I can't find how to discover whether its a webp or jpg but I'm pretty sure it'll be the jpg version.

Here's the link to the demo site

[gwpriester]

Downloads in my Firefox, Edge, Waterfox, and Brave browsers as webp Egg.

Shows fine in Safari, and Edge on my iPhone.

[Egg Bramhill]

Downloads in my Firefox, Edge, Waterfox, and Brave browsers as webp Egg.

I would expect this Gary.

Shows fine in Safari, and Edge on my iPhone.

Also expected as you have a fairly new iPhone with probably the latest version of Safari which now enables webp.

My question (and I believe Acorns) is older browsers downloading the jpg files?

[gwpriester]

Egg - I think Rob explained in one of these posts that the script searches for webp support and if it does not find the support then exports a straight JPG file.

[Acorn]

I would expect this Gary.
Also expected as you have a fairly new iPhone with probably the latest version of Safari which now enables webp.
My question (and I believe Acorns) is older browsers downloading the jpg files?

Egg, the WebP/JPEG/PNG equivalents are all present. There is code to detect when the browser can handle which and so every browser gets the right file format, except Internet Explorer, it would appear.

Acorn

[DanFelix]

One of my clients is an artist. His site contains about 40 works of art. When I use the WebP feature, the artwork appears watery and low res. When I post the site without using WebP then the artwork is once again clear and detailed. So, for now, I will have to refrain from using the feature on that site, regardless how it upsets Google's sensibilities.