[e10s] The option checked for <select> disappears when opened for the first time

NEW
Unassigned

Status

()

P2
normal
a year ago
10 months ago

People

(Reporter: over68, Unassigned)

Tracking

(Blocks: 1 bug, {regression})

55 Branch
x86_64
Windows 7
regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox53 unaffected, firefox54 unaffected, firefox55 fix-optional, firefox56 fix-optional, firefox57 ?)

Details

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Steps to reproduce:

1. Go to https://onedrive.live.com/download?cid=F96BA52A2AF70D03&resid=F96BA52A2AF70D03%211362&authkey=ACzTTnL6f5-eFoI.
2. Open the <select> element.


Actual results:

The option checked for <select> disappears and shows when opened for the first time.
Flags: needinfo?(jaws)
(Reporter)

Comment 1

a year ago
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b35e46dc0604&tochange=cf051de0d37b

Regressed by: bug 1352963
Blocks: 1352963
Keywords: regression
This is happening because we recreate all of the DOM nodes on transitionend during update. Instead of just deleting everything, we could compare what was previously used to create the menu with what was determined via the transitionend, and if it's not any different we can bail out of the update without replacing all of the nodes.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(jaws)
Comment hidden (mozreview-request)
I have attached a test that will fail if the nodes are removed, but I don't have time right now to implement the code that only updates what has changed.

Updated

a year ago
status-firefox53: --- → unaffected
status-firefox54: --- → unaffected
status-firefox55: --- → affected
Does it still reproduce? Seems OK here.
Flags: needinfo?(over68)
(Reporter)

Comment 6

a year ago
I can reproduce this bug with the latest nightly build.
Flags: needinfo?(over68)
status-firefox56: --- → affected
status-firefox55: affected → fix-optional
Priority: -- → P2
status-firefox56: affected → fix-optional
Does this still happen for 57?
status-firefox57: --- → ?
Blocks: 1409613
No longer blocks: 1154677
You need to log in before you can comment on or make changes to this bug.