Bug 1816059 Comment 13 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Tested a bit more to understand what overall improvement can we make while also offering a consistent UX for users.

I see that Chrome does two things differently and we should probably do the same.
Based on the attached video:
- show a [toast](https://developer.android.com/guide/topics/ui/notifiers/toasts) vs a [snackbar](https://m2.material.io/components/snackbars/android#snackbar)
This allows Chrome to show the fullscreen message on top of everything else.
This is something that we could easily do in Fenix (if approved by product and UX) but unfortunately styling options are non-existent for `toasts` and with Fenix using multiple `snackbars` all throughout the app this message will seem a bit out of place.
If we want to keep using snackbars the groundwork for showing them on top of any other Views was already done in https://bugzilla.mozilla.org/show_bug.cgi?id=1812518 and so we know it's possible. Medium size refactoring.
- the following line
`<select id="mySelect" onclick="document.documentElement.requestFullscreen();"`
does only one thing at a time:

  * first click will execute the `onClick` method 
  * another click is needed to show the select prompt.

Seems like they don't allow both actions at a time while Fenix does. Maybe this is something that can be implemented in Gecko also?
Tested a bit more to understand what overall improvement can we make while also offering a consistent UX for users.

I see that Chrome does two things differently and we should probably do the same.
Based on the attached video:
- show a [toast](https://developer.android.com/guide/topics/ui/notifiers/toasts) vs a [snackbar](https://m2.material.io/components/snackbars/android#snackbar)
This allows Chrome to show the fullscreen message on top of everything else.
This is something that we could easily do in Fenix (if approved by product and UX) but unfortunately styling options are non-existent for `toasts` and with Fenix using multiple `snackbars` all throughout the app this message will seem a bit out of place.
If we want to keep using snackbars the groundwork for showing them on top of any other Views was already done in https://bugzilla.mozilla.org/show_bug.cgi?id=1812518 and so we know it's possible. Medium size refactoring.
- the following line
`<select id="mySelect" onclick="document.documentElement.requestFullscreen();"`
does only one thing at a time:

  * first click will execute the `onClick` method 
  * another click is needed to show the select prompt.

Seems like they don't allow both actions at a time while Fenix does. Maybe this is something that can be implemented in Gecko also?
Regarding this scenario it seems like there is 2-way communication betwqeen the engine and the app: if after the first click that triggers entering in fullscreen the user exits this mode then the second screen will again enter fullscreen. I think this would significantly add to the complexity of the implementation.

Back to Bug 1816059 Comment 13