Open Bug 1595469 Opened 4 years ago Updated 1 year ago

[Win] Info panel not displayed on double clicking button + address bar

Categories

(Firefox :: Site Identity, defect, P5)

All
Windows
defect

Tracking

()

Tracking Status
firefox-esr68 --- unaffected
firefox70 --- wontfix
firefox71 --- wontfix
firefox72 --- fix-optional

People

(Reporter: cfogel, Unassigned)

Details

(Keywords: regression)

Attachments

(1 file)

Affected versions

  • 72.0a1 (2019-11-10), 71.0b8, 70.0.1,

Affected platforms

  • Windows 10,

Steps to reproduce

  1. Launch Firefox, access any https page ex. youtube and play the video;
  2. Double click on the address bar;
  3. Double click on the Site info button;
  4. (optional) Double click on the ETP button;
  5. (optional) Double click on the Site info button;
  6. Click on the Site info button until menu is displayed.

Expected result

  • button is set as pressed, menu displayed;

Actual result

  • button remains pressed, menu no longer displayed;
  • state persist when opening new tabs;

Regression range

  • range might be inaccurate since the issue is not really consistent and sometimes not manifested from the first attempt;
  • First bad: 2019-03-17 changeset: 1735fe85436911fca7c7e5837e4cbc94040b8825
  • Last good: 2019-03-16 changeset: 2a96d8f9339f49e84789bbe3899699c5d7185406
  • Pushlog: URL;

Additional notes

  • attached recording with the issue.
Has Regression Range: --- → yes
Has STR: --- → yes
Summary: [WIn]Info panel not displayed on double clicking button + address bar → [Win] Info panel not displayed on double clicking button + address bar

Affected versions
72.0a1 (2019-11-10), 71.0b8, 70.0.1,
Additional notes
71.0b8 not affected.

Cristian, could you clarify if 71 beta is affected or not? Thanks

Flags: needinfo?(cristian.fogel)

Beta 71 is affected as well.

Indeed, did not clear that part.
Due to the nature of the bug, I initially assumed that it's Ok; but while checking for the regression range it reproduced on the mentioned builds as well. Updating the note from the main comment as well.
Thank you for the ping!

Flags: needinfo?(cristian.fogel)

Nihanth, could you prioritize this bug and find an owner if this needs to be fixed in an upcoming release? Thanks

Flags: needinfo?(nhnt11)

Seems like a strange edge case that's "hard" to stumble into in a normal usage scenario, marking this P5 for now. If this issue is more severe than I'm interpreting please feel free to dispute the P5 verdict.

Flags: needinfo?(nhnt11)
Priority: -- → P5
Severity: normal → S3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.