Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mozilla expands extension support for Firefox for Android

blog.mozilla.org

Post reply on HN
Print view View original

61–70 of 251 posts

Re: Mozilla expands extension support for Firefox for Android

#62

Post by thomastjeffery »

ivanjermakov wrote: post #3
briffle wrote: post #2

I wish they would push hard for proper support in IOS for running extensions (or their own engine, etc)

I think it's still against Apple's TOS, stating that every web browser must be based on WebKit.

That's incredible. Just write anti-competitive behavior directly into the contract. No one will care.

Re: Mozilla expands extension support for Firefox for Android

#64

Post by 127361 »

sedatk wrote: post #48
mod50ack wrote: post #9

This is good. Now, all extensions marked by the developer as being compatible with Android are shown on AMO. (If you toggle to Desktop mode, you can actually install any other extension on AMO, too.) The baffling thing is why this took so damn long. FF for Android supported add-ons from the beginning. That's the best thing about Firefox for Android! They decided to rewrite the UI in 2020, and there were fair reasons…

[flagged]

And a chunk of Mozilla's funding going towards social justice related projects, as much of the organization has been co-opted by social justice types.

As was stated in the article[1], close to half a million dollars was spent on a social-justice related organization, the Mackenzie Mack Group.

“[Mckensie Mack Group] is a change management firm redefining innovation in the white-dominant change management industry.”

In the article it also says " While The Lunduke Journal does not like to delve too deeply into the Political Woods (tm), it should be questioned why so much money — possibly millions of dollars donated by individuals who thought they were supporting a web browser — is being funneled into highly political organizations that seem to have no involvement with the World Wide Web, Web Browsers, or any related standards. "

1. https://lunduke.locals.com/post/4387539/firefox-money-invest... "

Re: Mozilla expands extension support for Firefox for Android

#65

Post by bad_user »

sedatk wrote: post #48
mod50ack wrote: post #9

This is good. Now, all extensions marked by the developer as being compatible with Android are shown on AMO. (If you toggle to Desktop mode, you can actually install any other extension on AMO, too.) The baffling thing is why this took so damn long. FF for Android supported add-ons from the beginning. That's the best thing about Firefox for Android! They decided to rewrite the UI in 2020, and there were fair reasons…

[flagged]

That article actually shows that Mozilla spends most on software development.

It does have a lot of administrative overhead that it could do without, instead of laying off engineers, like they did. But the article itself is trash, due to complaining of $892,000 worth of expenses that seem dubious, in an organization that makes 500 million per year, which paints a certain kind of picture that's disingenuous.

Re: Mozilla expands extension support for Firefox for Android

#66

Post by ChrisArchitect »

ChrisArchitect wrote: post #7

We've had lots of news about this coming for months, but with Mozilla's quite low market share, and the share of those users that use extensions - who's really caring about this other than some power users?

Sensitive power users.

I didn't say it was sh*t. I'm saying it's not newsworthy.

Clap for the devs. And install all the extensions. But we don't need a hundred posts about it. This isn't the big story Firefox marketing might think it is.

Re: Mozilla expands extension support for Firefox for Android

#68

Post by gruez »

zamadatix wrote: post #57
firebot wrote: post #43

Earlier quoted context omitted.

Mine states 120.0.6099.26, which was released a month ago, https://chromereleases.googleblog.com/2023/11/chrome-beta-fo...

Your user agent string or the actual browser code? The former is notoriously just set to whatever makes websites happy. An easy way to test is see if a current feature actually works as expected e.g. https://jsfiddle.net/fxc9a8uc/1 "test1" should be green at the top right.

It's also possible that they updated the code but didn't push the changes to the repo, which I guess is better than running 15 month old code, but also is kinda suspicious because they're not honoring their commitment to open source.
Post reply on HN