[MGNLIMG-124] Imaging module upsampling Created: 13/Mar/14  Updated: 09/Sep/14  Resolved: 09/Sep/14

Status: Closed
Project: Imaging
Component/s: image operations
Affects Version/s: 3.0.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Geoffrey Perks Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS X Mavericks


Issue Links:
duplicate
duplicates MGNLIMG-45 Resizing: provide optional non-expansion Closed
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

 Description   

The imaging module has various classes which extend AbstractCropAndResize. The image is always resized to the max width and height specified in the configuration for an ImageGenerator. However, if in the generator's configuration, you specify dimensions 800 X 60, and upload an image into the DAM of 400 x 30 with the intent of rendering the image with the same dimensions; the image is always inflated to the max dimensions. Is there a way of preventing this from happening in order to keep the image's original size?


Generated at Mon Feb 12 02:12:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.