0055287: Incremental Input with expectedValue may be inconsistently aligned

Description

Right now, Incremental Input is supported with standard size. ( height : 5.6 rem )

Label and ExpectedValue inside BaseFormInput are displaced relatively to the Value inside with the following CSS rule:

transform: translate(-1.5rem, 0.85rem);

But this solution could be inconsistent when Incremental Input change his size or some styling rules are inherited from a current IncrementalInput used in POS2 and the input and expectedValue could be misaligned. ( i.e: In portrait Mode, incrementalInput size could be smaller )

InputAdornment is another case to avoid the padding when there is no ClearInput or AddtitionalButtons on the right side of the BaseFormInput.

Steps To Reproduce

Proposed Solution

Avoid the use of transform relative from the Input Value, and change it with a consistent alignment from the parent.

Buttons "+" and "-" on both sides should scale its size depending on the height defined.

Tags

No tags attached.

Attached Files

Screenshot from 2024-04-22 19-16-19.png [^] (2,708 bytes) 2024-04-22 19:19

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

feature request

0055154

closed

ablasco

Incremental Input Improvements

Notes
(0177527) hgbot (developer) 2025-03-27 12:13	Issue exported to Jira: https://openbravo.atlassian.net/browse/RM-24260 [^]

Issue History
Date Modified	Username	Field	Change
2024-04-22 19:19	ablasco	New Issue
2024-04-22 19:19	ablasco	Assigned To	=> Triage Platform Base
2024-04-22 19:19	ablasco	File Added: Screenshot from 2024-04-22 19-16-19.png
2024-04-22 19:19	ablasco	OBNetwork customer	=> No
2024-04-22 19:19	ablasco	Triggers an Emergency Pack	=> No
2024-04-23 09:45	ablasco	Relationship added	related to 0055154
2024-04-23 09:58	ablasco	Proposed Solution updated
2025-03-27 12:13	hgbot	Note Added: 0177527
2025-03-27 12:13	hgbot	Status	new => closed
2025-03-27 12:13	hgbot	Resolution	open => duplicate