Closed Bug 1625604 Opened 5 years ago Closed 5 years ago

Cannot select multiple items of <select multiple> on GeckoView nightly 76.0.20200327094805

Categories

(GeckoView :: General, defect)

76 Branch
Other
Android
defect
Not set
normal

Tracking

(firefox-esr68 unaffected, firefox74 unaffected, firefox75 unaffected, firefox76+ fixed)

RESOLVED FIXED
mozilla76
Tracking Status
firefox-esr68 --- unaffected
firefox74 --- unaffected
firefox75 --- unaffected
firefox76 + fixed

People

(Reporter: masayuki, Assigned: emilio)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

  1. Go to Advanced Search of bugzilla
  2. Tap the list of Component
  3. Tap another item in Component

Expected: The first item stays selected.
Actual: Only the second tapped item is selected.

Previously, tapping <select multiple> opens popup to choose items. But now, it does not appear. Regressed at least a couple of weeks ago, IIRC.

I don't think this is a regression.

I'm able to replicate the issue on the latest GeckoView example app that uses GeckoView nightly, this is a regression, as I'm not able to replicate the issue on GeckoView Beta version.

To reproduce use this example page. It looks like the issue is linked to a change in how we render and attach events to HTML elements. In this video, you can see the difference between nightly (Geckoview Sample app) and Beta(Fenix) on how a select element is rendered also how the events are reacting differently. In nightly(Geckoview Sample app) the even of selecting is only getting triggered when the label for the select element is clicked while in Beta(Fenix) the event is getting triggered when the select element is clicked.

Component: Widget: Android → General
Product: Core → GeckoView
Summary: Cannot select multiple items of <select multiple> on Fenix → Cannot select multiple items of <select multiple> on GeckoView nightly 76.0.20200327094805
Version: Trunk → 76 Branch

Sounds like fallout from bug 1618202 then.

Depends on: 1618202
Has Regression Range: --- → yes
Assignee: nobody → emilio
Flags: needinfo?(emilio)

This is a bit hacky, but is how it used tow work without the native theme. We
may be able to do better.

<input type="date"> / <input type="time"> work the same way with and without the
other two selectors, because they never match since we moved them to shadow DOM
in Firefox 65 (bug 1496242).

Flags: needinfo?(emilio)
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5e377369f9d0 Move pointer-events: none declaration for option to forms.css. r=snorp
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: