Closed
Bug 1208989
Opened 10 years ago
Closed 10 years ago
Dragging icons in customize mode is very jarring and jumpy
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
DUPLICATE
of bug 1206418
People
(Reporter: quicksaver, Unassigned)
Details
(Keywords: regression, reproducible)
In the latest nightly when I enter customize mode and try to move any icons in the palette, instead of fluid movements I see jumpy and flickering icons.
Last good build: https://hg.mozilla.org/mozilla-central/rev/37c7812ce0e6d10c7e7182f12e752832835e1d67 [1]
First bad build: https://hg.mozilla.org/mozilla-central/rev/eb30e5ee32f0a11e3df594b5b3e69d0a5566bb63 [2]
Regression window: https://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2015-09-18+11%3A20&enddate=2015-09-18+20%3A49
[1] http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/1442575192/
[2] http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/1442609376/
Updated•10 years ago
|
Keywords: regression,
reproducible
Comment 2•10 years ago
|
||
Sinker, any chance this was your patches?
Luís, can you doublecheck the same with mozregression against inbound?
Flags: needinfo?(tlee)
Flags: needinfo?(quicksaver)
| Reporter | ||
Comment 3•10 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #2)
> Luís, can you doublecheck the same with mozregression against inbound?
Confirmed: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=5b52aac3102684d57140b1eda99f56eb37b4f285&tochange=621ab19e86db28c38bbbf9119fbf6831ea344c54
Flags: needinfo?(quicksaver)
Comment 4•10 years ago
|
||
Luis, please check bug 1206418, it may be the same problem.
If it's not, a video is helpful.
Flags: needinfo?(tlee)
| Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Thinker Li [:sinker] from comment #4)
> Luis, please check bug 1206418, it may be the same problem.
> If it's not, a video is helpful.
Indeed, I don't see this issue in the latest inbound. I guess it was the same problem. (I didn't dissect exactly which build/patch fixed it, I don't think it's necessary as it was almost surely bug 1206418 as you suggested.)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•