Gecko 155.0.1.186 for Windows 10 Mobile

Gecko 155 (Firefox 155.0.1) for Windows 10 Mobile, ARM, build 155.0.1.186.

Requirements: Windows 10 Mobile 1703 (15063) or newer, interop unlock (the package declares restricted capabilities: codeGeneration for the JIT, file-system access for the profile), the signing certificate Gecko.cer trusted on the phone. See INSTALL.txt. It installs over 155.0.1.140 and keeps the profile.

Changes since 155.0.1.140

Everyday use

• Copy and paste work with the phone's clipboard, both ways.
• The keyboard no longer hides and pops back up while text is being selected in the address bar and other fields.
• The Back button closes the keyboard, an open menu or dialog, fullscreen or the address bar being edited, goes back in the tab's history, closes a tab a page opened back to its opener, and only then sends the browser to the background.
• Downloads go to Downloads\Gecko (or a folder chosen in the settings), "Save as" works, and so do the system file pickers, uploads and opening downloaded files.
• Taps in landscape land where the finger is; quick taps (captchas, small buttons) register; a feed that scrolls while it loads no longer jumps, and flings feel like Firefox for Android.
• Text on pages made for computers (no mobile layout) is enlarged to a readable size, as Firefox for Android does.
• Discord and WhatsApp Web get their desktop versions after login.
• Permission prompts (the microphone and others) fit the screen and sit above the system's bar.

Video, calls and web platform

• VK Video: no more crash on the pre-roll ad or when switching videos (a new hardware decoder now waits a moment after the previous one ended; this worked around a stack overflow in the Adreno driver).
• Microphone for WebRTC: sites get the permission prompt, the phone's own consent is asked the first time, and the microphone works more than once per run.
• WebAssembly works again.
• VP9 and AV1 are turned down on every site that also offers H.264, not only on YouTube, so video goes to the hardware decoder.

Memory and stability

• The browser watches its 32-bit address space (2 GB per process) and gives memory back before an allocation fails, not after.
• Collections under memory pressure are rationed: on a Lumia 650 they used to freeze the interface for 5-20 seconds; now they are rare pauses of 1-3 seconds.
• The interface archives are compressed: about 70 MB less address space taken.
• Fixed the picture freezing after the keyboard closed when memory was short (Elite X3 with Discord): the browser took taps but the screen no longer updated.
• The session is saved again with many tabs and closed tabs.
• Fixed hangs at start and the crash when answering the system's microphone prompt.
• Phones with more than 1.5 GB of RAM get a more economical JavaScript heap growth profile.

Low-end phones (Lumia 650 and similar, Direct3D feature level 9_3)

• Fewer flashes of old video frames.
• After a video frame only the area that changed is redrawn, not the whole screen.

Logs (Settings > About > Verbose logs for debugging, as before)

• The log says what the network did for slow or failed pages, what memory is used for, and what garbage collection cost. Addresses lose their query strings, and nothing from private windows is logged.

Known issues

• The camera in WebRTC has not been tested; only the microphone has.
• Extensions run on the same thread as pages: uBlock Origin slows the browser noticeably even when switched off from its own menu. Disable it in about:addons.
• Heavy web apps (Discord) can run into the 2 GB address space and stutter.
• A video that starts right after another one (after an ad, for example) may start about a second later.
• VP9 and AV1 are decoded in software and do not play well above 360p.
• A Lumia 650 is still much slower than an Elite X3.

Tested on HP Elite X3 (Snapdragon 820, 4 GB RAM) and Lumia 650 (Snapdragon 212, 1 GB RAM).

Gecko 155.0.1.140 for Windows 10 Mobile

Gecko 155 (Firefox 155.0.1) for Windows 10 Mobile, ARM, build 155.0.1.140.

Requirements: Windows 10 Mobile 1703 (15063) or newer, interop unlock (the package declares restricted capabilities: codeGeneration for the JIT, file-system access for the profile), the signing certificate Gecko.cer trusted on the phone. See INSTALL.txt.

In this build

• Hardware WebRender on the GPU (ANGLE / Direct3D 11) with partial present.
• JIT for JavaScript.
• Hardware H.264 decoding (DXVA); playing video goes to the display's hardware overlay when nothing of the page is drawn over it: fullscreen 60 fps video in portrait and landscape (frames are turned ahead of the display's rotation in landscape).
• Vsync from the display's vertical blank (no more ~56 Hz software timer).
• Windows a page opens are tabs, sign-in popups (Google, VK...) included; the site gets the result and closing the popup returns to it.
• Quiet logs by default (Settings > About > Verbose logs for debugging).

Changes since 155.0.1.139: sign-in popups open as tabs.

Tested on HP Elite X3 (Snapdragon 820, 4 GB RAM) and Lumia 650 (Snapdragon 212, 1 GB RAM: runs, but slowly).

Gecko 155.0.1.139 for Windows 10 Mobile

Gecko 155 (Firefox 155.0.1) for Windows 10 Mobile, ARM, build 155.0.1.139.

Requirements: Windows 10 Mobile 1703 (15063) or newer, interop unlock (the package declares restricted capabilities: codeGeneration for the JIT, file-system access for the profile), the signing certificate Gecko.cer trusted on the phone. See INSTALL.txt.

In this build

• Hardware WebRender on the GPU (ANGLE / Direct3D 11) with partial present.
• JIT for JavaScript.
• Hardware H.264 decoding (DXVA); playing video goes to the display's hardware overlay when nothing of the page is drawn over it: fullscreen 60 fps video in portrait and landscape.
• Vsync from the display's vertical blank (no more ~56 Hz software timer).
• Quiet logs by default (Settings > About > Verbose logs for debugging).

Tested on HP Elite X3 (Snapdragon 820, 4 GB RAM) and Lumia 650 (Snapdragon 212, 1 GB RAM: runs, but slowly).