2026-05-22T22:44:39Z https://yabu.me LINux on MOBile https://yabu.me/npub1cc9aps8e7nszxwu3v98r9harszug098f63kelmup74d47yy77p0sqfzrg3 https://linuxmobile.social/fileserver/01WDKZKKD3V1T7QWQ75ER8CRP2/attachment/original/01JX5EZEWR853FTGHA3J6Y3NEE.png https://linuxmobile.social/fileserver/01WDKZKKD3V1T7QWQ75ER8CRP2/attachment/original/01JX5EZEWR853FTGHA3J6Y3NEE.png https://yabu.me/nevent1qqszh25c963g87w3ms5w3hdtvh5ppy4zeaq78tv5dmkluvn8yqtccsgzyrrqh5xql86wqgemj9s5uvkl5wqt3pu5a82xm8l0s864khcsnmc97dvjucm Knowing that mobile-config-firefox 4.6.0 is not providing a great experience with current Firefox ≥ 140, <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1clclcgsk2yv949g73nzf8c3utsd44c080xshqf4c2z44huq3a9dq9eemga" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Oliver Smith</span> (<span class="italic">npub1clc…emga</span>)</a></span> and I have decided that it would be good to land a small 4.6.1 releases with minimal changes (mostly README) on top of current master, as that at least fixes the poor URL bar behavior.<br/><br/>To make sure to avoid regressions, this is the testing requirement I&#39;ve come up with:<br/><br/>&#34;Test master as before tagging on<br/>- Sxmo<br/>- stable<br/>- esr<br/>- current<br/>- edge<br/>- esr<br/>- current<br/>- Plasma Mobile<br/>- stable<br/>- esr<br/>- current<br/>- edge (on USB cursed OP 6)<br/>- esr<br/>- current<br/>- Phosh<br/>- stable (on Librem 5)<br/>- esr<br/>- current<br/>- edge (on OP 6 256)<br/>- esr<br/>- current<br/>- GNOME Shell<br/>- stable<br/>- esr<br/>- current<br/>- edge<br/>- esr<br/>- current<br/>- Droidian<br/>- with what ever they ship<br/>- Mobian<br/>- Bookworm (PinePhone?)<br/>- esr<br/>- Trixie (2nd Librem 5, I guess?)<br/>- esr&#34;<br/><br/><br/>Why is that?<br/><br/>1. There&#39;s still Firefox 128 lurking in some places. IMHO, you should not use it any more for mobile, as 140 has scrollable popups (no more fiddly scrollbar fun) - but for the lifetime of Alpine 3.22/pmOS 25.06, we&#39;ll unfortunately still have to deal with it.<br/><br/>2. Different wayland compositors (or different releases of the same compositor) may cause different behavior with popups.<br/><br/>If there&#39;s anything missing in that list and there&#39;s something else I should add to my testing list, please tell! 2025-09-09T06:55:22Z