Bugzilla

(In reply to Botond Ballo [:botond] from comment #37)
> My understanding is that at this point, this bug only affects configurations where the "minimal toolbar" is enabled

I can still reproduce some trouble in default-configured Nightly on Android, though it's not as bad as it was originally.  Nowadays, the problem is that the "Type a message" textfield is *partially* covered by the keyboard. I'll attach a screenshot of Firefox vs. Chrome.  (This is with current Nightly on my Pixel 10 Pro XL as well as my Pixel 6a.)

> I'm not sure what is the best way to reflect this in the bug flags -- maybe this shouldn't be a site-report any more? For now I am resetting the Webcompat Priority flag.

In cases where conditions have changed such that the score feels inaccurate, the best way to recompute the score is to update the data that feeds into it using the Site Issue Triage tool https://addons.mozilla.org/en-US/firefox/addon/site-issue-triage/  (click the lightbulb icon at top right of url bar when viewing this bug, and then select "Triage" from the dropdown menu, and then adjust fields as-needed).
 
Given that I'm seeing this still reproduce but to a lesser extent, I'm going to suggest we downgrade  "Notable annoyance" to "Minor annoyance", which moves the score from 300 to 50, which feels reasonable I think.

(In reply to Botond Ballo [:botond] from comment #37)
> My understanding is that at this point, this bug only affects configurations where the "minimal toolbar" is enabled

I can still reproduce some trouble in default-configured Nightly on Android, though it's not as bad as it was originally.  Nowadays, the problem is that the "Type a message" textfield is *partially* covered by the keyboard, when the keyboard appears (and then you can scroll to fully reveal it). I'll attach a screenshot of Firefox vs. Chrome.  (This is with current Nightly on my Pixel 10 Pro XL as well as my Pixel 6a.)

> I'm not sure what is the best way to reflect this in the bug flags -- maybe this shouldn't be a site-report any more? For now I am resetting the Webcompat Priority flag.

In cases where conditions have changed such that the score feels inaccurate, the best way to recompute the score is to update the data that feeds into it using the Site Issue Triage tool https://addons.mozilla.org/en-US/firefox/addon/site-issue-triage/  (click the lightbulb icon at top right of url bar when viewing this bug, and then select "Triage" from the dropdown menu, and then adjust fields as-needed).
 
Given that I'm seeing this still reproduce but to a lesser extent, I'm going to suggest we downgrade  "Notable annoyance" to "Minor annoyance", which moves the score from 300 to 50, which feels reasonable I think.