Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Datagrid: UI Overlap between RowStatus and SetDirtyIndicator #4918

Closed
NarraVivek opened this issue Mar 5, 2021 · 5 comments · Fixed by #4999
Closed

Datagrid: UI Overlap between RowStatus and SetDirtyIndicator #4918

NarraVivek opened this issue Mar 5, 2021 · 5 comments · Fixed by #4999
Assignees
Labels
type: bug 🐛 [2] Velocity rating (Fibonacci)

Comments

@NarraVivek
Copy link

NarraVivek commented Mar 5, 2021

Describe the bug
The datagrid component has an overlap with the rowstatus() icon and setDirtyIndicator() icon with the 1st cell of each row.

To Reproduce
setDirtyIndicator() to true with an active rowStatus().

Steps to reproduce the behavior:

  1. Go to https://design.infor.com/code/ids-enterprise/latest/demo/components/datagrid/example-editable?theme=uplift&variant=light
  2. Click on "Add Row Status".
  3. Create a breakpoint using the dev tools.
  4. Once the row status are highlighted, execute $('#datagrid').data('datagrid'). setDirtyIndicator(3,0,true)
  5. Observe the row status icon to be broken/popping out with an yellow color.
  6. For additional information, please take a look into the attached screenshot.

Expected behavior
Row Status/Dirty indicator should not be broken or merging with each other.

Version
ids-enterprise: v4.37.0
ids-enterprise-ng: v9.2.0

Screenshots
Screenshot_7
Screenshot_8

Platform

  • Infor Application/Team Name: Infor PIM
  • OS Version: Windows 10
  • Browser Name: chrome
@tmcconechy tmcconechy changed the title Datagrid: having conflicts with RowStatus and SetDirtyIndicator Datagrid: UI Overlap between RowStatus and SetDirtyIndicator Mar 5, 2021
@tmcconechy tmcconechy added [2] Velocity rating (Fibonacci) type: bug 🐛 labels Mar 5, 2021
@tmcconechy tmcconechy added this to To do in Enterprise 4.51.x (Apr 2021) Sprint via automation Mar 5, 2021
@tmcconechy
Copy link
Member

Will have to see whats possible here. Ideally the dirty indicator lays over the other. But they might be using the same element.
If thats the case then one may need to take precedence over the other. i.e. if dirty AND a status then only show the status as that implies it would be dirty too. Just no broken layout woud be the goal

@rob2d
Copy link
Contributor

rob2d commented Mar 25, 2021

@tmcconechy @NarraVivek

Am not familiar with the functional side of things here yet and am not very experienced with Angular but: would it be invasive to add an extra div for indicating a dirty marker, or put it on another layer? the reason I ask is I am not sure the client use case and if it would cause regressions in client selector code.

It seems td[role='gridcell']::before is used for both the dirty indicator and the status triangle currently, so don't think it can be done without changing markup.

For a solution am thinking we could have an ::after div for the dirty indicator (moving that in front/off of current as that seems more of a secondary function), and add a pointer-events: none on this.

Alternatively, we can also change the dirty marker as well as corner triangle to be in an inline SVG to be conceptually simpler for the CSS.

@tmcconechy
Copy link
Member

ok thats what i thought might happen. So then i suggest we just do what i said for now and set a precedence sort of thing. I.E. both status cannot be shown in the same cell. So effectively just

  • if class rowstatus-cell
  • turn off the css for td.is-dirty-cell::before

Its sort of wierd that the first cell is dirty (its a checkbox cell) so i think that will work

One other issue i see we should address is try selecting a row and you will see the status is cut off

@rob2d
Copy link
Contributor

rob2d commented Mar 25, 2021

In that case, thanks for the clarification Tim 👍

@jbrcna
Copy link
Contributor

jbrcna commented Mar 31, 2021

the issue is now resolved. v4.39.0-dev
https://master-enterprise.demo.design.infor.com/components/datagrid/test-dirty-indication.html
image

@jbrcna jbrcna moved this from Ready for QA (master) to Done in Enterprise 4.50.x (Mar 2021) Sprint Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug 🐛 [2] Velocity rating (Fibonacci)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants