We have moved to GitHub Issues
Created by Mark Owen 24 May 2017, 15:58:02 Updated by Mark Owen 25 May 2017, 11:04:53
What did you do?
What did you expect to happen?
What actually happened?
On investigation I noticed an intimidate few issues that could be resolve in one way or another:
I also tried in a couple of other browsers and this issue presented worst, by far, in Chrome, but still wasn't great in others.
It looks as if there are only 2 FileResolvers both that have the width of the image loaded hardcoded to 500. Feels like this should be parameterised. Since there are only 2 both with the same option I think it should be possible to change the signature of FileResolvers to (property, entity, thumbnail, width) with it falling back to width 500 if not set, but passed in in the case above to be smaller. One step in the right direction.
Also as far as I can tell the entire function setOriginalSize in the MediaGridDirective is unrequired if the images were sized correctly when requested from the server. ImageProcessor supports width, height and a mode of max that will do what this method seems to do.
Backwards Compatible: True
Affected versions: 7.5.3
Due in version: