Conversation
|
@davisagli thanks for creating this Pull Request and helping to improve Plone! TL;DR: Finish pushing changes, pass all other checks, then paste a comment: To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically. Happy hacking! |
src/plone/volto/profiles/default/registry/plone.base.interfaces.controlpanel.IImagingSchema.xml
Show resolved
Hide resolved
|
@jenkins-plone-org please run jobs |
|
@davisagli A curiosity. If the image isn't 2k, these new scales won't be generated, correct? |
|
@wesleybl In Plone 6 scales are generated on demand the first time they are downloaded. We generate the metadata which lists the scales in 2 different places:
|
|
@davisagli Are the larger scales generated by the RESTAPI returned to the srcset attribute? If so, is there a risk that the browser might select them, resulting in distorted images? |
|
@sneridagh I added an upgrade step.
Not distorted images, but when the original image is very large, we start giving the browser more options for serving a smaller one. We also have to set |
|
@jenkins-plone-org please run jobs |
Co-authored-by: Maurits van Rees <maurits@vanrees.org>
This is needed to avoid a reduction in image quality from plone/volto#7655
I didn't add an upgrade step yet but we probably should (careful to only add the new scales, and not change others)