(In reply to Timothy Nikkel (:tnikkel) from comment #2) > We also haven't gotten a regression range from someone seeing this using https://mozilla.github.io/mozregression/ which pin point which change in Firefox (if any) caused this. To emphasize: if this bug is affecting you (in a clean profile / with no addons), and you've got 20-30 minutes to spare, **please** consider using the mozregression tool to find the change that introduced the regression. We've had multiple reports of this, but have been unable to reproduce it ourselves, and without a regression window from someone who _can_ reproduce it, we are unlikely to be able to reach a diganosis and fix.
Bug 1768330 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Timothy Nikkel (:tnikkel) from comment #2) > We also haven't gotten a regression range from someone seeing this using https://mozilla.github.io/mozregression/ which pin point which change in Firefox (if any) caused this. To emphasize: if this bug is affecting you (in a clean profile / with no addons), and you've got 20-30 minutes to spare, **please** consider using the mozregression tool to find the change that introduced the regression. We've had multiple reports of this, but have been unable to reproduce it ourselves, and without a regression window from someone who _can_ reproduce it, we are unlikely to be able to reach a diganosis and fix. If you have questions about how to set up or use the mozregression tool, we're happy to provide details.
(In reply to Timothy Nikkel (:tnikkel) from comment #2) > We also haven't gotten a regression range from someone seeing this using https://mozilla.github.io/mozregression/ which pin point which change in Firefox (if any) caused this. To emphasize: if this bug is affecting you (in a clean profile / with no addons), and you've got 20-30 minutes to spare, **please** consider using the mozregression tool to find the change that introduced the regression. We've had multiple reports of this, but have been unable to reproduce it ourselves, and without a regression window from someone who _can_ reproduce it, we are unlikely to be able to reach a diagnosis and fix. If you have questions about how to set up or use the mozregression tool, we're happy to provide details.