I have this site and on retina screens all the phone screen pics look sharp.
On non-retina screens however the phone screens in the first section at the top look fine, but in the sections below the text on the screens breaks up.
It is doing this in Chrome, Safari, Opera. But not in Firefox.
I have no idea why this is happening all the pics are the same size and they have all been marked as HiDPI.
Can anyone help please?
Here’s a screengrab, the text on the image on the left with the dark background is more readable than the text on the right hand image.
I don’t know if this helps but I’ve cloned the site, re-imported the phone images (which are smaller) and turned off the interactions on three of the sections.
CVLT fitness the new social workout app
WORKOUTS
JOIN A GROUP
And on a non-retina screen the images are all clearer and you can read the text within the image.
I’ve left interactions on for the last section
LEADERBOARDS
And the text within the image is blocky.
Is there a problem with the interactions I have created?
All sections look fine on Safari, starting at the second section, they look choppy on Chrome (OS X). Can you post your read only link? Share a read-only link | Webflow University
Everything looks fine on the interaction to me–hopefully someone else can chime in and teach us both a bit about this! One side note, if you right click the phone in Chrome and hit Inspect Element, unchecking this code forces Chrome to smooth the image out:
I know that doesn’t help much, but it’s something I observed!
You shouldn’t have to manually code any of this. Webflow is top-notch when it comes to outputting code that works. Have you emailed them at support@webflow.com? Really curious about an answer to this!
These Webflow 2D transforms on Chrome (OS X) do not properly render, appearing noticeably jagged, particularly on a non-retina display as documented by Glenn_Ashcroft. This problem seems to be documented on Stack Overflow with a popular fix that Webflow does not seem to employ.
Edit 2: This seems to be much larger than just Chrome for OS X, it seems to also affect images on Chrome for Windows, the most used desktop browser in the world. See screenshot: