Closed Bug 1740439 Opened 4 years ago Closed 4 years ago

Zoom selection dropdown doesn’t open on codepen.io website

Categories

(Core :: Layout: Form Controls, defect)

defect

Tracking

()

VERIFIED FIXED
96 Branch
Tracking Status
firefox-esr91 --- wontfix
firefox94 --- wontfix
firefox95 --- wontfix
firefox96 --- verified

People

(Reporter: asoncutean, Assigned: emilio)

References

(Regression)

Details

(Keywords: regression)

Attachments

(3 files)

Attached image screencast_issue.gif

Affected versions

  • 96.0a1 (2021-11-10)
  • 95.0b5
  • 94.0.1

Affected platforms

  • Windows 10
  • macOS 11.0
  • Ubuntu 16

Steps to reproduce

  1. Open https://codepen.io/MSEdgeDev/pen/mxeOGW
  2. Resize the browser width in order to trigger the zoom scale dropdown appearance on the page footer
  3. Click on the zoom scale dropdown

Expected result

  • The dropdown is expanded

Actual result

  • The dropdown attempts to open, flickers a second, but it doesn't expand

Regression range

Other notes

  • Works on Chrome and Safari
  • There is no message inside the browser console
Has Regression Range: --- → yes
Has STR: --- → yes

Probably the same cause as 1305017.

Attached file Reduced test-case.

Set release status flags based on info from the regressing bug 1253486

Assignee: nobody → emilio
Status: NEW → ASSIGNED

The root cause is bug 1440506 but the patch above avoids the reframe altogether which is nice.

See Also: → 1440506
Component: DOM: Events → Layout: Form Controls
See Also: → 1740474, 1740609, 1305017, 1448813
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/50ee7770e823 Improve the avoid-reframing-when-changing-cb optimization to work with buttons and select elements. r=dholbert
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/31595 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
Upstream PR merged by moz-wptsync-bot

Verified fixed with latest Nightly Fx 96 (2021-11-22) on Windows 10, Ubuntu 20.04, macOS 12.1.

Status: RESOLVED → VERIFIED

Is it risky to uplift this bug to 91ESR?

Flags: needinfo?(emilio)

It depends on a few other optimizations like bug 1735533 and so on. Not opposed to try rebasing all that if you think it's worth it, but it does feel a little bit scary. It's probably fine if there's a good reason though, what would be the reasoning for that? (Other than "slightly annoying bug"?)

Flags: needinfo?(emilio) → needinfo?(alice0775)

I just encountered this bug on the website https://www.plus-a.net/uranai/ .
I wish I could work around it with user CSS and scripting....

Flags: needinfo?(alice0775)

On that page you can work around it with something like .searchform select { transform: translate(0, 0) } or so

(In reply to Emilio Cobos Álvarez (:emilio) from comment #15)

On that page you can work around it with something like .searchform select { transform: translate(0, 0) } or so

Ok, Thanks for the hints!
The following user CSS is a workaround.

.form:active {
    position:unset!important;
    top: unset!important;
}
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: