Unable to click on form fields after first change event, positioning seems skewed
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
People
(Reporter: brizental, Unassigned)
References
(Regression)
Details
(Keywords: regression)
The title of this bug is probably not descriptive to what it exactly is, since I haven't really investigated to understand what is the underlying cause.
This regression can be reproduced here: https://rainy-quartz.surge.sh/user/metrics/timing_distribution.html#simulator and it only reproduces for Firefox Nightly, currently I am using version 81.0a1 (2020-08-08) (64-bit)
on MacOS.
The steps to reproduce are:
- Go to the "Simulator" section of the page and change any one of the fields under "Properties" or "Data options";
- Try clicking on one of the other fields, notice you'll be unable to click on any of them, sometimes text on the graph will be highlighted while clicking of these inputs which makes me think maybe this is related to positioning issues;
- EXTRA: If you scroll up and go back down you'll be able to click on the other form fields again, everytime you change one you'll have to scroll up and back down to be able to click.
I say this is a regression because it works for Stable. I bisected this on mozregression and it found that this issue was introduced by: https://phabricator.services.mozilla.com/D78136
Obs.: The demo link provided is a temporary link, if it is not working anymore that might mean this interface is not in the demo phase anymore and should now live in https://mozilla.github.io/glean/book/user/metrics/timing_distribution.html#simulator
Comment 1•4 years ago
|
||
I don't trust the mozregression run in comment #0 since it is pointing to just test changes, so I ran mozregression myself and I think it is related to bug 1644271. This issue is somewhat intermittent so regression hunting is a little error prone. I looked at the regressions from bug 1644271 and this seems probable. Kats, can you take a look here?
Comment 2•4 years ago
|
||
Yeah it seems quite probably a regression from bug 1644271 as it is similar in symptoms to the other regressions. It should be fixed soon once bug 1543485 lands. I'll dupe to the existing bug we have tracking this problem and verify the fix once it lands.
Updated•4 years ago
|
Comment 3•4 years ago
|
||
I verified this is fixed in the latest nightly.
Description
•