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

Agama "flashes" congratulations screen before installation begins #1616

Open
lkocman opened this issue Sep 17, 2024 · 3 comments
Open

Agama "flashes" congratulations screen before installation begins #1616

lkocman opened this issue Sep 17, 2024 · 3 comments
Labels
good first issue Good for newcomers ux UX related bugs/improvements

Comments

@lkocman
Copy link
Contributor

lkocman commented Sep 17, 2024

Hello team

there seems to be a glitch where congratulations screen flashes (like for a second or so) before the installation progress bar is displayed. Which means right after clicking the install button.

This of course confuses openQA if we're waiting for congratulations screen which signalizes end of installation :-)

I can workaround it to ensure that we match installation progress first and then match congratulations.
So definitely low prio, but people might notice this glitch.

(see the timestamp of the glitch which can be then found in attached webm file)
image
congratulations.webm

@lkocman lkocman changed the title Agama "flashes" congratulations screen before installation begins this confuses openQA! Agama "flashes" congratulations screen before installation begins Sep 17, 2024
lkocman added a commit to lkocman/os-autoinst-distri-opensuse that referenced this issue Sep 17, 2024
* Agama seems to randomly flash congratulations screen
  before installation begins. This confuses openQA
  gh#agama-project/agama#1616

* Workaround is to ensure we see installation progress screen first
lkocman added a commit to lkocman/os-autoinst-distri-opensuse that referenced this issue Sep 17, 2024
* Agama seems to randomly flash congratulations screen
  before installation begins. This confuses openQA
  gh#agama-project/agama#1616

* Workaround is to ensure we see installation progress screen first
@lkocman lkocman added good first issue Good for newcomers ux UX related bugs/improvements labels Sep 17, 2024
@dgdavid
Copy link
Contributor

dgdavid commented Sep 18, 2024

Ouch! Great catch! Thanks for reporting it 😃

but people might notice this glitch.

Sure, something to be fixed sooner than later.

JFTR, I suspect the problem is mix between

https://github.com/openSUSE/agama/blob/bc057f474f9783717f355af970440e7215b2b705/web/src/App.jsx#L60-L62

and

https://github.com/openSUSE/agama/blob/bc057f474f9783717f355af970440e7215b2b705/web/src/components/core/Installation.jsx#L26

For some reason, the Installation.jsx component is reached when is not busy first 🤷‍♂️

First solution that comes to my mind is to drop the Installation.jsx component which is acting as a "router" and move its logic to the App.jsx comonponent which, guess what, is a "router" too. We are aware that App.jsx deserves improvements too, but maybe such a movement could avoid that ugly and unexpected glitch.

@dgdavid
Copy link
Contributor

dgdavid commented Sep 18, 2024

to drop the Installation.jsx component which is acting as a "router

Which was initially a less dummy component (see 11cca00#diff-5e04ed7cc51a6f8b3424160cdfeb3aa05b11a5143431092843446a676c914211) but it has become in a dispensable component.

Funny thing is that it was introduced for reducing blinking 😆 but that was so long ago with a completely different frontend architecture.

@lkocman
Copy link
Contributor Author

lkocman commented Sep 20, 2024

Thank you @dgdavid for looking into it! We have a workaround in place so no rush.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers ux UX related bugs/improvements
Projects
None yet
Development

No branches or pull requests

2 participants