-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird behaviour with very large images #5
Comments
This is intended behavior. There is, as always in Symphony, no direct relation between the backend and the frontend. Too large images get scaled down via JIT to reduce load times. But the cropping is always relative to the original size. If you want to preview the image in a different size, you can use the |
What about adding a field setting to set the size of the preview image, shown as an additional link in the "Actions" part on the publish page? This way you can synchronize the display of the image in back- and front-end. |
Bump. |
Sorry! Yeah I think that'd be useful so an Author can get a feel before they save the entry of what's going to appear on the frontend. |
Will implement an additional preview setting in 1.1. |
I'm not sure if anything can be done in this regard, but if working with an image that is larger than the Cropping area, it appears that the image is scaled to fit the cropping area, so when you drag the handles to crop a particular area it doesn't actually apply a 'crop and scale'.
Instead it crops to this area, but when you preview the image, it is the cropped area, but at the original scale.
I suppose this relates to Issue #2, because in my scenario, we'd like to limit the client to a particular size image and have whatever they upload be scaled and cropped to fit x*y dimensions.
The text was updated successfully, but these errors were encountered: