134.0.2 - affected(In reply to Bob from comment #50) > Would it be possible to also test release 134 or one of the nightlies before this patch to see if Poco on Android 14 worked before? Given Pixel still fires the old key handlers I wonder if Poco is doing the same thing. I tested the Firefox 134.0.2 build on the Poco device, and it’s also affected. Additionally, I ran a regression on the Nightly and here are the results: - Last good build: 134.0a1 (Build #2016056106), hg-7d29edd4cb62+, GV: 134.0a1-20241114095720, AS: 134.20241109050310, 2024-11-14T13:53:07.413545876 - First bad build: 134.0a1 (Build #2016056194), hg-0191fbfc9115+, GV: 134.0a1-20241114211619, AS: 134.20241114050344, 2024-11-15T00:02:14.728580427(In reply to Bob from comment #51) > Sure, I'm happy to work on it but will definitely need help with testing. Will move further Android 13 discussion over to that bug. The QA team would be happy to assist with this testing, as we have several physical devices with Android 13.
Bug 1932300 Comment 52 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 Bob from comment #50) > Would it be possible to also test release 134 or one of the nightlies before this patch to see if Poco on Android 14 worked before? Given Pixel still fires the old key handlers I wonder if Poco is doing the same thing. I tested the Firefox 134.0.2 build on the Poco device, and it’s also affected. Additionally, I ran a regression on the Nightly and here are the results: - Last good build: 134.0a1 (Build #2016056106), hg-7d29edd4cb62+, GV: 134.0a1-20241114095720, AS: 134.20241109050310, 2024-11-14T13:53:07.413545876 - First bad build: 134.0a1 (Build #2016056194), hg-0191fbfc9115+, GV: 134.0a1-20241114211619, AS: 134.20241114050344, 2024-11-15T00:02:14.728580427(In reply to Bob from comment #51) > Sure, I'm happy to work on it but will definitely need help with testing. Will move further Android 13 discussion over to that bug. The QA team would be happy to assist with this testing, as we have several physical devices with Android 13.
(In reply to Bob from comment #50) > Would it be possible to also test release 134 or one of the nightlies before this patch to see if Poco on Android 14 worked before? Given Pixel still fires the old key handlers I wonder if Poco is doing the same thing. I tested the Firefox 134.0.2 build on the Poco device, and it’s also affected. Additionally, I ran a regression on the Nightly and here are the results: - Last good build: 134.0a1 (Build #2016056106), hg-7d29edd4cb62+, GV: 134.0a1-20241114095720, AS: 134.20241109050310, 2024-11-14T13:53:07.413545876 - First bad build: 134.0a1 (Build #2016056194), hg-0191fbfc9115+, GV: 134.0a1-20241114211619, AS: 134.20241114050344, 2024-11-15T00:02:14.728580427 (In reply to Bob from comment #51) > Sure, I'm happy to work on it but will definitely need help with testing. Will move further Android 13 discussion over to that bug. The QA team would be happy to assist with this testing, as we have several physical devices with Android 13.