Enterprise: TrackDirty: indictor not on the checkboxes component when scrolling

[CindyMercadoReyes]

Describe the bug
Checkboxes component disappears on responsive view

To Reproduce
Steps to reproduce the behavior:

1. Go to url: http://4120-beta0-enterprise.demo.design.infor.com/
2. Scroll down to Checkboxes and click on the dirty tracker checkbox
3. Make the page responsive
4. All the checkboxes are no longer appearing. However you can still see the dirty tracker ticker on the UI

Expected behavior
The checkboxes component should appear when the page is on responsive view

Screenshots

Platform

• MAC Chrome

Additional context
Add any other context about the problem here.
None

[tmcconechy]

They are in the page, its just scrolling. I think the solution here is to make the dirty tracker not absolutely positioned in the page..

[EdwardCoyle]

This isn't quite as simple as it looks. I'm not totally familiar with the dirty tracking code, but the dirty trackers on these checkboxes aren't wrapped inside of a common element along with the checkboxes, making their placement a bit tricky for situations where the page repaints columns/containers/etc.

Specifically for Checkboxes/Radios, we may be looking at attaching the absolute positioning routine in the TrackDirty component to the global resize handler

@tmcconechy @deep7102, what do you guys think?

[tmcconechy]

Can we take another approach by perhaps adding a "is-dirty" class to either the label or input that adds a pseudo element that styles the tick instead of a seperate element?

[EdwardCoyle]

Not sure that we can... the pseudo-elements are reserved for the checkbox in the case of the label wrapping the input

[tmcconechy]

What about on the field wrapper? Also can we just make it relative? Seems to break the styling but not sure why.

[tmcconechy]

Had another look at this issue and i cant seem to reproduce it on http://4180-enterprise.demo.design.infor.com/ or http://4190-rc1-enterprise.demo.design.infor.com/

So placing as fixed in 4.20 for further re-verification

[brianjuan]

Yeah, it seems like fixed on the latest version, tested in http://localhost:4000/ on all browsers, will retest once beta is deployed.