Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce this particular issue using a fresh nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 -potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. Some notes (might only be applicable for the affected Win 11): - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. - The one time I managed to reproduce with Nova enabled, I used an Fx Account to sync bookmarks/history, waited a few minutes, then restarted the browser. Unfortunately I don't have more concise STR than that, as we're still trying to figure out exactly how to trigger the original issue. Windows 11 affected specs: -Scale: 125%(recommended) -Display resolution: 1920x1080(recommended) -Display orientation: Landscape Please let us know if you would prefer a new bug for the scenario mentioned in this comment. We'll resume the investigation again as soon as we can. Thank you!
Bug 2050821 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce this particular issue using a fresh nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 -potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. Some notes (might only be applicable for the affected Win 11): - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. - The one time I managed to reproduce with Nova enabled, I used an Fx Account to sync bookmarks/history, waited a few minutes, then restarted the browser. Unfortunately I don't have more concise STR than that, as we're still trying to figure out exactly how to trigger the original issue. Windows 11 affected specs: - Scale: 125%(recommended) - Display resolution: 1920x1080(recommended) - Display orientation: Landscape Please let us know if you would prefer us to file a new bug for the scenario mentioned in this comment particularly. Thank you!
Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce this particular issue using a fresh nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 - potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. Some notes (might only be applicable for the affected Win 11): - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. - The one time I managed to reproduce with Nova enabled, I used an Fx Account to sync bookmarks/history, waited a few minutes, then restarted the browser. Unfortunately I don't have more concise STR than that, as we're still trying to figure out exactly how to trigger the original issue. Windows 11 affected specs: - Scale: 125%(recommended) - Display resolution: 1920x1080(recommended) - Display orientation: Landscape Please let us know if you would prefer us to file a new bug for the scenario mentioned in this comment particularly. Thank you!
Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce using a fresh Nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 - potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. Some notes (might only be applicable for the affected Win 11): - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. - The one time I managed to reproduce with Nova enabled, I used an Fx Account to sync bookmarks/history, waited a few minutes, then restarted the browser. Unfortunately I don't have more concise STR than that, as we're still trying to figure out exactly how to trigger the original issue. Windows 11 affected specs: - Scale: 125%(recommended) - Display resolution: 1920x1080(recommended) - Display orientation: Landscape Please let us know if you would prefer us to file a new bug for the scenario mentioned in this comment particularly. Thank you!
Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce using a fresh Nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 - potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. This might only be applicable for the affected Win 11. Windows 11 affected specs: - Scale: 125%(recommended) - Display resolution: 1920x1080(recommended) - Display orientation: Landscape Please let us know if you would prefer us to file a new bug for the scenario mentioned in this comment particularly. Thank you!
Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce using a fresh Nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 - potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. Narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. This might only be applicable for the affected Win 11. Windows 11 affected specs: - Scale: 125%(recommended) - Display resolution: 1920x1080(recommended) - Display orientation: Landscape Please let us know if you would prefer us to file a new bug for the scenario mentioned in this comment particularly. Thank you!
Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce using a fresh Nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 - potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. Narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. This might only be applicable for the affected Win 11. Windows 11 affected specs: - Scale: 125%(recommended) - Display resolution: 1920x1080(recommended) - Display orientation: Landscape Later edit: We also managed to reproduce with a fresh Firefox Nightly profile on Ubuntu 24. Please let us know if you would prefer us to file a new bug for the scenario mentioned in this comment particularly. Thank you!
Hi! We tested and investigated a combination of scenarios in which we tried to isolate concise STR for the cropped input issue. On my end, I managed to reproduce using a fresh Nightly profile. I managed to isolate a regression range using mozregression on the machine I could reproduce reliably. The regression range is far newer than the date this bug was logged, and it might be a different issue altogether that the one reported here, albeit very similar. - last good: 2026-07-07; - first bad: 2026-07-08; - pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=26c8191dfbef7a6ca4570a847a2924d45309951e&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42 - potential regressor: bug 2050692 We can log a new bug for this particular regression range if it's preferable, as it seems to only affect Windows 11 at the moment. Also, please note that we only managed to reproduce this particular scenario on a single Windows 11 machine. We were unsuccessful in reproducing on macOS 13 or a different Windows 11 desktop. - Interestingly, toggling browser.nova.enabled on true will reproduce the issue only on maximised windows. Narrower browser windows do not crop the input. This is only with Nova enabled, however. With Nova disabled the browser window size seems inconsequential. This might only be applicable for the affected Win 11. Windows 11 affected specs: - Scale: 125%(recommended) - Display resolution: 1920x1080(recommended) - Display orientation: Landscape Later edit: We also managed to reproduce with a fresh Firefox Nightly profile on Ubuntu 24. Please let us know if you would prefer us to file a new bug for the scenario mentioned in this comment particularly, or track the issue here further. Thank you!