Skip to content
This repository has been archived by the owner on Dec 2, 2021. It is now read-only.

[MLMD Lineage] UI scale is too large for a laptop display #193

Closed
kwasi opened this issue Dec 16, 2019 · 1 comment · Fixed by #199
Closed

[MLMD Lineage] UI scale is too large for a laptop display #193

kwasi opened this issue Dec 16, 2019 · 1 comment · Fixed by #199

Comments

@kwasi
Copy link
Contributor

kwasi commented Dec 16, 2019

/kind feature

Background

Currently the UI uses key widths from the original UX mocks. These sizes don't scale down well to a laptop monitor. This video shows that:

  • The user has to scroll horizontally back and forth to explore forward and backward lineage
  • The full 5 columns don't fit on the page.

Describe the solution you'd like

  • Minimum: Scale the UI down so it fits on a 1680x1050 screen
  • Better: Scale down the UI to fit comfortably in 800 pixels of width
  • Better: Write the card/column widths to fill the available width

Anything else you would like to add:

  • Consider:
    • A few key widths for different screen sizes
    • Having a maximum card width and center the UI for extremely wide displays
@kwasi kwasi changed the title UI move around too much when using the first and last columns [Lineage] UI scale is too large for a laptop display Dec 16, 2019
@kwasi
Copy link
Contributor Author

kwasi commented Dec 16, 2019

/area metadata
/area front-end

@kwasi kwasi changed the title [Lineage] UI scale is too large for a laptop display [MLMD Lineage] UI scale is too large for a laptop display Dec 17, 2019
@avdaredevil avdaredevil moved this from To do to In progress in Pipelines: MLMD Lineage FE Dec 20, 2019
@avdaredevil avdaredevil moved this from In progress to Review in progress in Pipelines: MLMD Lineage FE Jan 6, 2020
@avdaredevil avdaredevil self-assigned this Jan 6, 2020
Pipelines: MLMD Lineage FE automation moved this from Review in progress to Done Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants