|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
Bug 1358975 - Test to confirm that nodes shouldn't change on transitionend if value and label are unchanged.
59 bytes, text/x-review-board-request
|Details | Review|
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.
Regression range: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b35e46dc0604&tochange=cf051de0d37b Regressed by: bug 1352963
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
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.
status-firefox53: --- → unaffected
status-firefox54: --- → unaffected
status-firefox55: --- → affected
Does it still reproduce? Seems OK here.
I can reproduce this bug with the latest nightly build.
status-firefox56: affected → fix-optional
Does this still happen for 57?
status-firefox57: --- → ?
I can still reproduce this bug in https://onedrive.live.com/download?cid=F96BA52A2AF70D03&resid=F96BA52A2AF70D03%211480&authkey=AMq45IS6QuDeKhQ.
You need to log in before you can comment on or make changes to this bug.