[meta] QA testing of Olivero across multiple browsers

Should we do the same with assistive technology like NVDA & VoiceOver?

Added child issues for individual browser testing. WIll add issues as they are created, thanks.

Still need to determine what functions will need to be tested.

Will there be different things to test on mobile and desktop browsers?

Thread from Drupal slack: https://drupal.slack.com/archives/CJT807H7T/p1632752290045700?thread_ts=...

Andy
Just went digging into the bartick, seven, claro, and umami issue queues and none of them have issues specifically for browser testing the project as a whole.

Was there a specific maintainer that said we needed whole-project browser testing or is that an issue we put on ourselves?

https://www.drupal.org/node/3079238
Contributors manually test significant changes in multiple browsers to watch for regressions, but this is somewhat based on the contributors available and the particular issue. We do not yet have full automated browser testing for our supported browsers.
This sounds like browser testing is required for each individual feature, but not necessarily as a whole.

If a maintainer did request this, could they advise or provide guidance? TIA!

The following browser QA issues have been tested, reviewed, and listed as fixed.

#3210745: QA testing of Olivero - Desktop browser: Google Chrome
#3210751: QA testing of Olivero - Desktop browser: Internet Explorer
#3210752: QA testing of Olivero - Mobile browser: UC Browser

Just went digging into the bartick, seven, claro, and umami issue queues and none of them have issues specifically for browser testing the project as a whole.

Bartik and Seven were added during the major development cycle (i.e. before minor releases and experimental), and then there were issues like #2152519: [meta] Make sure Drupal 8 looks good and works right on browsers (both mobile+desktop) to retrospectively test them before release.

Umami is perma-experimental so there hasn't been a step where it's marked stable.

Claro isn't stable yet.

So Olivero is the first new core theme to go from experimental to stable in any meaningful way, meaning we don't have any clear precedents.

My personal feeling here is that there's been a lot of informal testing of Olivero on multiple browsers, and some of that could have been documented on this issue earlier in the process, to save having to retest everything at the end - even if that might not have meant a formal script run-through probably would have been enough. Having said that can't have too much testing.

Parenting to making it the default now.

I found an issue on the Olivero test site where the progress percentage displays directly next to the progress message within AJAX progress and AJAX small progress with no spacing between the text and the percentage. I initially noticed this while testing the progress bars doing QA on Safari, but I also verified the same issue exists on all browsers I've tested. This includes browsers marked as fully tested with their QA issues closed, so posting here. This particular issue exists in the latest versions of Safari, Chrome, Firefox, IE 11, Edge, and Brave, so I would have to say it's across the board. See the attached screenshot taken on a desktop screen at 1080P.

All issues from the roadmap have been closed!

I added a comment on the Firefox one earlier, it is very difficult to read the search placeholder for me:
https://www.drupal.org/project/drupal/issues/3210746
Should I create a specific issue?

@phjou yes please create a new issue!