[RESPDAM-78] Image doesn't always match the closest option if no variation is specified on the URL Created: 01/Dec/22  Updated: 21/Dec/22  Resolved: 02/Dec/22

Status: Closed
Project: DAM Focal
Component/s: commons
Affects Version/s: 2.3.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Adrien Manzoni
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive focalNoVariationUrlLM.zip    
Issue Links:
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Team: Services

 Description   

Steps to reproduce:

1 - Add the attached light module to your Magnolia instance.

2 - Request any image through the focalpoint with an url similar to this:
.imaging/focalpoint/400x239/dam/jcr:ab2c4750-f59a-4b45-87f3-ec27de99d1a5/kitchen.jpg
 
Even though the requested width is defined by the last variation on the configuration file, it returns the image with a 700 pixels width rather than 400.
This behaviour is altered if you play around moving the variations order, like defining the variation that allows 400px width on the first place rather than the last.



 Comments   
Comment by Raphael Falvo [ 02/Dec/22 ]

That was not a bug, misunderstanding about the closest match which is done against ratio, not height or width. Also having 2 variations with same ratio in the config might lead to unexpected results

Generated at Mon Feb 12 00:42:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.