Bug

Too tired to find the right place for this, noting it down here for the moment.

On #GitHub, mobile #Firefox, at least with my settings, is not showing the “Code” drop-down button that includes the URLs for cloning a repo.

Sure, i can construct it manually, but it’s more convenient this way.

Desktop Firefox shows it. Mobile Chrome shows it.

Firefox on #Android doesn’t. (Tablet+keyboard+SSH client is decent for remote building at least)

Gotta look up where to file a bug report. Tomorrow.

On Wandering.shop

@Fixato confirms it and finds a related blog post

Interesting…it’s not quite the same – I was trying to copy the clone URL to paste into an ssh app, and it showed the Fork and related menus just fine on my tablet screen.

But asking for the desktop site *does* work! Even if it looks otherwise identical to what I was seeing on the “mobile” version because the screen’s big enough!

I guess large tablet screens on mobile OSes are kind of a gray area as far as whether the experience is properly “mobile” or just portable!

Add-on for Firefox that can do web page translation locally

This looks cool: #mozilla has released an add-on for #firefox that can do web page #translation *locally* instead of sending data to the cloud.

Mozilla releases local machine translation tools as part of Project Bergamot

The translations add-on is now available in the Firefox Add-On store for installation on Firefox Nightly, Beta and in General Release.

Based on Project Bergamot and implemented in WebAssembly

it’s one of those things like speech recognition that ideally should have always have been local, but the processing and data just wasn’t there yet

On Wandering.shop
On Twitter
Expanded on Blog

Ah, so that’s what’s going on. All my Firefox add-ons are disabled because the intermediate …

Ah, so that’s what’s going on. All my Firefox add-ons are disabled because the intermediate signing cert expired, so it can’t verify ANY of them.

Not too thrilled at having my privacy add-ons remotely disabled, mind you. I appreciate checking signatures on installation/upgrade, but that shouldn’t introduce a remote dependency on a single point of failure to keep using things that have *already* been verified.

https://www.engadget.com/2019/05/03/firefox-extension-add-on-cert/

#firefox #broken

On Wandering.shop

Flashback to last summer: a red panda (sometimes called a fire fox)…

Flashback to last summer: a red panda (sometimes called a fire fox) at the San Diego Zoo. I made a point to look for them and the penguins on that trip. For reasons. 😉

#photography #photos #redpanda #firefox

On Photog.Social

Sadly I didn’t get to see them doing much. There were several in the enclosure, maybe three or four, but the rest were either hiding in the tree or sleeping. This one was just sort of perched up there, looking around.

On Photog.Social

One of the problems with Mozilla’s plan to hide Firefox version numbers…

One of the problems with Mozilla’s plan to hide Firefox version numbers is that the replacement of “You’re running the latest version” only succeeds if people have confidence that the check is working. Speaking for myself, the last time I checked About:Firefox, I was convinced that it was broken until I verified that the update I was expecting was Mac-only, which was why it wasn’t showing up on Windows.

The biggest, of course, is breaking deeply ingrained user expectations (where to find the version number) for no real discernible benefit.

Removing Firefox Version Number – mozilla.dev.usability