My build environment is an Ubuntu 24.04 VM.
Turns out I wasn’t running npm install in my build script, but that also apparently isn’t the issue: building after an npm install results in an equally broken (i.e. iconless) build as without it.
I’ll attach an output log from the npm install part. It at least mentions postinstall.sh.
I don’t know; depends on whether it is run as part of the documented npm run build:android build command, which is what I’m using.
After updating my build of the mobile app from 2.40.0 to 2.41.1 (and no other changes in the build environment), all icons in the resulting app have been replaced with a ”☒”, and all channel icons with what looks like a Chinese character (the app is supposed to use English, like the OS). Only user profile pictures seem unaffected (except for the overlaid status indicator, which *is* affected).
I’ve so far tested this on a phone running Android 10 and a tablet running Android 15. Both are using the ”Onyx” theme (and switching the theme has no impact on the issue). The server is running the latest release 11.8.1 (and the web UI is unaffected).
Sorry, I was tracing this on a test site using a mockup, and apparently the <span> is actually only added once the post is published, so the issue doesn’t manifest when using previews. That’s why I never caught it while actually writing the posts and using previews, only after publishing.
The trailing <span class="__iawmlf-post-loop-links"> element introduced in PR #338 causes WordPress to render a trailing newline as a <br /> tag in the last paragraph. This behavior differs from when Link Fixer is not active.
I don’t know if the block editor is affected, since I don’t use it, but the issue is present when using the Classic Editor, and even there you have to use the Code view (because Visual view either converts the trailing newline into a line with an , or strips the trailing newline when switching to Code view).
My guess is that this is wpautop trying to be smart about the content, seeing the trailing <span> from Link Fixer, and thinking it’s visible content, so the trailing newline in the actual content (as entered in the editor) should be rendered as a visible <br /> too.
This is probably a very niche issue, and I’m sure I can figure out a way to work around it, but I wanted to document it anyway.
</p> tagthe <span> to immediately follow the last word and immediately precede the closing </p> tag, with no newline before or after
the <span> is separated from the last word with a <br /> tag followed by a plain newline
Can we get an RSS feed for the OS Server releases? I’ve been following the Network Application releases feed, but now that it’s bundled in, I gather that we should be following releases of the OS Server instead.
Yup, I haven’t been able to trigger the issue anymore lately. Thank you for the fix!
I fired up 152.0a1 (from nightly), did my steps above, and could no longer reproduce the issue. So it does seem to be fixed!
Garmin Connectissa kyllä saa, ja on aina saanut, valita oletuspyörän, että ei niitä tarvi käsin suorituksiin lisätä. Viimeisimmän uudistuksen myötä sinne tuli myös pyörän osien kategoria, ja näitä voi niputtaa kokonaisuuksiksi, jotka nekin voi liittää oletuksena kaikkiin pyöräilyihin.
Voisi se vieläkin joustavampi olla: oletusvälineet ovat lajikohtaisia, eivät lajiprofiilikohtaisia. Eli jos samaa lajia (vaikkapa maantiepyöräilyä) ajaa useammalla eri pyörällä, joutuu niitä ei-oletuspyörällä ajettuja sitten rukkaamaan jälkikäteen.
I know I’m not the one the request was directed to, but I’ve attached my log anyway. What I did to produce it:
1. MOZ_LOG="WidgetScreen:5,WidgetWayland:5,Widget:5,WidgetPopup:5" /usr/bin/firefox >log.txt 2>&1
2. opened the Wikipedia article for Firefox
3. powered off both my monitors, then powered them back on
4. tried right-clicking many of the links on the page
5. quit Firefox