### Update Whew, this has been quite the chain of regressions! My plan is to uplift this patch into Firefox 126 Beta. I'll provide a summary of all the events, as well as the final resulting behaviors of all the Firefox versions. --- ### Breakdown of Events 1) This regression was caused by Bug 1870327 in Firefox 125. 2) Following that, I attempted to fix the regression by fixing Bug 1889697, which was uplifted into Firefox 125. 3) Unfortunately, that patch fixed most of the issue, but caused a different extremely-unlikely-to-happen-in-the-wild regression in the panel's error messaging, which was fixed by Bug 1892541 and uplifted into Firefox 126. 4) But then I realized that Bug 1889697 didn't quite fix all of the issue caused by Bug 1870327. It fixed it for opening multiple new windows all on their own, but there was still one edge case left where you drag a pre-existing tab to become its own window. 5) This bug fixes that and adds a test case for that specific scenario. --- ### Summary of behavior in each Firefox version Assuming this gets uplifted into Firefox 126 beta, the resulting state of everything will be the following: * **Firefox 124** will work as expected. * **Firefox 125** will have only the issue described by this bug, where dragging an open tab to a new window and then opening the FullPageTranslationsPanel will fail to populate the dropdown menus **only** if the panel was opened already in the previous window. However the user will be able to fix the initialization state if they attempt to open the panel from a new tab that was crated within the new window from the start. There are no security risks here, just a minor edge-case inconvenience that is easily fixable by the user. * **Firefox 126** will work as expected.
Bug 1893776 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### Update Whew, this has been quite the chain of regressions! My plan is to uplift this patch into Firefox 126 Beta. I'll provide a breakdown of all the events, as well as a summary of the final resulting behaviors of all the Firefox versions. --- ### Breakdown of Events 1) This regression was caused by Bug 1870327 in Firefox 125. 2) Following that, I attempted to fix the regression by fixing Bug 1889697, which was uplifted into Firefox 125. 3) Unfortunately, that patch fixed most of the issue, but caused a different extremely-unlikely-to-happen-in-the-wild regression in the panel's error messaging, which was fixed by Bug 1892541 and uplifted into Firefox 126. 4) But then I realized that Bug 1889697 didn't quite fix all of the issue caused by Bug 1870327. It fixed it for opening multiple new windows all on their own, but there was still one edge case left where you drag a pre-existing tab to become its own window. 5) This bug fixes that and adds a test case for that specific scenario. --- ### Summary of behavior in each Firefox version Assuming this gets uplifted into Firefox 126 beta, the resulting state of everything will be the following: * **Firefox 124** will work as expected. * **Firefox 125** will have only the issue described by this bug, where dragging an open tab to a new window and then opening the FullPageTranslationsPanel will fail to populate the dropdown menus **only** if the panel was opened already in the previous window. However the user will be able to fix the initialization state if they attempt to open the panel from a new tab that was crated within the new window from the start. There are no security risks here, just a minor edge-case inconvenience that is easily fixable by the user. * **Firefox 126** will work as expected.
### Update Whew, this has been quite the chain of regressions! My plan is to uplift this patch into Firefox 126 Beta. I'll provide a breakdown of all the events, as well as a summary of the final resulting behaviors of all the Firefox versions. --- ### Breakdown of Events 1) This regression was caused by Bug 1870327 in Firefox 125. 2) Following that, I attempted to fix the regression by fixing Bug 1889697, which was uplifted into Firefox 125. 3) Unfortunately, that patch fixed most of the issue, but caused a different extremely-unlikely-to-occur regression in the panel's error messaging, which was fixed by Bug 1892541 and uplifted into Firefox 126. 4) But then I realized that Bug 1889697 didn't quite fix all of the issue caused by Bug 1870327. It fixed it for opening multiple new windows all on their own, but there was still one edge case left where you drag a pre-existing tab to become its own window. 5) This bug fixes that and adds a test case for that specific scenario. --- ### Summary of behavior in each Firefox version Assuming this gets uplifted into Firefox 126 beta, the resulting state of everything will be the following: * **Firefox 124** will work as expected. * **Firefox 125** will have only the issue described by this bug, where dragging an open tab to a new window and then opening the FullPageTranslationsPanel will fail to populate the dropdown menus **only** if the panel was opened already in the previous window. However the user will be able to fix the initialization state if they attempt to open the panel from a new tab that was crated within the new window from the start. There are no security risks here, just a minor edge-case inconvenience that is easily fixable by the user. * **Firefox 126** will work as expected.
### Update Whew, this has been quite the chain of regressions! My plan is to uplift this patch into Firefox 126 Beta. I'll provide a breakdown of all the events, as well as a summary of the final resulting behaviors of all the Firefox versions. --- ### Breakdown of Events 1) This regression was caused by Bug 1870327 in Firefox 125. 2) Following that, I attempted to fix the regression by fixing Bug 1889697, which was uplifted into Firefox 125. 3) Unfortunately, that patch fixed most of the issue, but caused a different extremely-unlikely-to-occur regression in the panel's error messaging, which was fixed by Bug 1892541 and uplifted into Firefox 126. 4) But then I realized that Bug 1889697 didn't quite fix all of the issue caused by the original regressor Bug 1870327. It fixed it for opening multiple new windows all on their own, but there was still one edge case left where you drag a pre-existing tab to become its own window. 5) This bug fixes that and adds a test case for that specific scenario. --- ### Summary of behavior in each Firefox version Assuming this gets uplifted into Firefox 126 beta, the resulting state of everything will be the following: * **Firefox 124** will work as expected. * **Firefox 125** will have only the issue described by this bug, where dragging an open tab to a new window and then opening the FullPageTranslationsPanel will fail to populate the dropdown menus **only** if the panel was opened already in the previous window. However the user will be able to fix the initialization state if they attempt to open the panel from a new tab that was crated within the new window from the start. There are no security risks here, just a minor edge-case inconvenience that is easily fixable by the user. * **Firefox 126** will work as expected.
### Update Whew, this has been quite the chain of regressions! My plan is to uplift this patch into Firefox 126 Beta. I'll provide a breakdown of all the events, as well as a summary of the final resulting behaviors of all the Firefox versions. --- ### Breakdown of Events 1) This regression was caused by Bug 1870327 in Firefox 125. 2) Following that, I attempted to fix the regression by fixing Bug 1889697, which was uplifted into Firefox 125. 3) Unfortunately, that patch fixed most of the issue, but caused a different extremely-unlikely-to-occur regression in the panel's error messaging, which was fixed by Bug 1892541 and uplifted into Firefox 126. 4) But then I realized that Bug 1889697 didn't quite fix all of the issue caused by the original regressor (Bug 1870327). It fixed it for opening multiple new windows all on their own, but there was still one edge case left where you drag a pre-existing tab to become its own window. 5) This bug fixes that and adds a test case for that specific scenario. --- ### Summary of behavior in each Firefox version Assuming this gets uplifted into Firefox 126 beta, the resulting state of everything will be the following: * **Firefox 124** will work as expected. * **Firefox 125** will have only the issue described by this bug, where dragging an open tab to a new window and then opening the FullPageTranslationsPanel will fail to populate the dropdown menus **only** if the panel was opened already in the previous window. However the user will be able to fix the initialization state if they attempt to open the panel from a new tab that was crated within the new window from the start. There are no security risks here, just a minor edge-case inconvenience that is easily fixable by the user. * **Firefox 126** will work as expected.
### Update Whew, this has been quite the chain of regressions! My plan is to uplift this patch into Firefox 126 Beta. I'll provide a breakdown of all the events, as well as a summary of the final resulting behaviors of all the Firefox versions. --- ### Breakdown of Events 1) This regression was caused by Bug 1870327 in Firefox 125. 2) Following that, I attempted to fix the regression by fixing Bug 1889697, which was uplifted into Firefox 125. 3) Unfortunately, that patch fixed most of the issue, but caused a different extremely-unlikely-to-occur regression in the panel's error messaging, which was fixed by Bug 1892541 and uplifted into Firefox 126. 4) But then I realized that Bug 1889697 didn't quite fix all of the issue caused by the original regressor (Bug 1870327). It fixed the issue for opening multiple new windows all on their own, but there was still one edge case left where you drag a pre-existing tab to become its own window. 5) This bug fixes that and adds a test case for that specific scenario. --- ### Summary of behavior in each Firefox version Assuming this gets uplifted into Firefox 126 beta, the resulting state of everything will be the following: * **Firefox 124** will work as expected. * **Firefox 125** will have only the issue described by this bug, where dragging an open tab to a new window and then opening the FullPageTranslationsPanel will fail to populate the dropdown menus **only** if the panel was opened already in the previous window. However the user will be able to fix the initialization state if they attempt to open the panel from a new tab that was crated within the new window from the start. There are no security risks here, just a minor edge-case inconvenience that is easily fixable by the user. * **Firefox 126** will work as expected.
### Update Whew, this has been quite the chain of regressions! My plan is to uplift this patch into Firefox 126 Beta. I'll provide a breakdown of all the events, as well as a summary of the final resulting behaviors of all the Firefox versions. --- ### Breakdown of Events 1) This regression was caused by Bug 1870327 in Firefox 125. 2) Following that, I attempted to fix the regression by fixing Bug 1889697, which was uplifted into Firefox 125. 3) Unfortunately, that patch fixed most of the issue, but caused a different extremely-unlikely-to-occur regression in the panel's error messaging, which was fixed by Bug 1892541 and uplifted into Firefox 126. 4) But then I realized that Bug 1889697 didn't quite fix all of the issue caused by the original regressor (Bug 1870327). It fixed the issue for opening multiple new windows all on their own, but there was still one unhandled edge case where a user can drag a pre-existing tab to become its own window, causing the panel initialization to still fail if it was already initialized in the previous window. 5) This bug fixes that and adds a test case for that specific scenario. --- ### Summary of behavior in each Firefox version Assuming this gets uplifted into Firefox 126 beta, the resulting state of everything will be the following: * **Firefox 124** will work as expected. * **Firefox 125** will have only the issue described by this bug, where dragging an open tab to a new window and then opening the FullPageTranslationsPanel will fail to populate the dropdown menus **only** if the panel was opened already in the previous window. However the user will be able to fix the initialization state if they attempt to open the panel from a new tab that was crated within the new window from the start. There are no security risks here, just a minor edge-case inconvenience that is easily fixable by the user. * **Firefox 126** will work as expected.