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

Firefox 68.0

mozilla.org

Post reply on HN
Print view View original

201–210 of 282 posts

Re: Firefox 68.0

#201

Post by aflag »

callahad wrote: post #163
icebraining wrote: post #150

Earlier quoted context omitted.

Will Preview be guaranteed to support extensions before Firefox for Android goes EOL?

I can't make any specific commitment, but there's a lot of time between now and Firefox for Android going EOL (and we haven't committed to specific timing for that, either.) However, we do have concrete plans for supporting adblocking as a built-in feature in the near future ( https://github.com/mozilla-mobile/fenix/issues/96 ), which should make Preview more palatable to folks who rely on add-ons for that, even if o…

But if Firefox 69 is not coming to Android it means it has already EOLed, doesn't it?

Re: Firefox 68.0

#202

Post by _njyk »

hu3 wrote: post #122
_njyk wrote: post #79

Earlier quoted context omitted.

Kiwi Browser (Chromium-based) runs Nano Adblocker and uBlock Origin with full support (like on Firefox)

Thanks! I'm investigating it and sadly it seems a bit stale with last commit made 5 months ago: https://github.com/kiwibrowser/android For browsers this seems like a bit too long without updates. I can imagine maintaining such project is demanding but hopefully the project can gain more attention now with the new version of Firefox breaking extensions on Android.

There are almost daily builds on Discord if you want to join

Re: Firefox 68.0

#203

Post by DiabloD3 »

dralley wrote: post #141
Causality1 wrote: post #123

Earlier quoted context omitted.

Then why can extensions still not customize the UI, even for something as simple as putting the tabs below the address and bookmarks bar?

That's what UserChrome.css is for.

I don't know why this guy was downvoted, he's correct.

I even have a pretty decent UserChrome.css to better integrate Tree Style Tab, https://www.reddit.com/r/FirefoxCSS/comments/ao3ydl/configur...

Re: Firefox 68.0

#204

Post by silversconfused »

I was absolutely mozilla's target audience when firefox was introduced. Now they remove control and capabilities from us, and I keep getting told here on HN I'm not their target audience, and should accept that they are making this for "most users" who need extension signing, auto updates, sandboxing, and in general NERFING THE POWER from me. Who the hell are they building for if not techies? Who do they think is going to evangelize for them if not techies?

Mozilla: fix it.

Re: Firefox 68.0

#205

Post by DiabloD3 »

agumonkey wrote: post #180
dblohm7 wrote: post #135

Earlier quoted context omitted.

That's placebo -- Nightly is built from our trunk. The only thing that changes between Nightly 69 and Nightly 70 is a version bump.

no it's not something is definitely different somewhere, maybe a different config/default or reset, everything is snappier and my cpu is reaching 95+ degC while it never reached 80 before 70. Or maybe it's a different rendering library / os / gpu driver interaction.

Maybe you crossed into having webrender enabled for your system?

Re: Firefox 68.0

#206

Post by silversconfused »

Endy wrote: post #32

I'll be downvoted to Hell for this, but I don't care. With each subsequent release of Firefox, I'm consistently happy that I've moved to Pale Moon. The nonsense they're adding and the problems that Mozilla has to "fix" seem more often than not to be brought on themselves with the rapid-release and the move away from being Firefox to being "almost Chrome". The move to multi-process (which has introduced memory leaks),…

Mozilla has been pushing anti-features like their survival depends on it. I too have moved to forks. I use icecat and waterfox now. Tired of being abused because they assume too much. Just be a stupid browser and stop being the internet police. You're not making the web better, you're just driving your long time users (we hackers) away, and news flash, no one is there to replace them! Normal users use default tools.

Re: Firefox 68.0

#207

Post by JaimeThompson »

callahad wrote: post #142
kevin_b_er wrote: post #47

This marks the last Android release with extensions/add-on support. There will not be a 69 release of this edition of Firefox for Android ("Fennec"). The new remake of the mobile browser ("Fenix") does not have extensions support and it is on an indefinite and easily ignorable backlog. It is explicitly not being worked on this quarter. At the end of this quarter is the scheduled release of Firefox 69. Unless there's…

Hi. I work for Mozilla. Firefox for Android is not dead. You are free to continue using it. It will continue to support add-ons, and it will receive regular security updates and bugfixes for at least the next year. We are focusing all new feature development in Firefox Preview, but we're continuing to support Firefox for Android as an Extended Support Release while we build Preview. And, for what it's worth, we do un…

To be honest that is one of the most Fortune 500 style responses I have ever read coming out of someone involved in Mozilla. I mean what does 'we are taking that into account in our planning." actually mean?

Re: Firefox 68.0

#208

Post by modzu »

modzu wrote: post #68
kevin_b_er wrote: post #47

This marks the last Android release with extensions/add-on support. There will not be a 69 release of this edition of Firefox for Android ("Fennec"). The new remake of the mobile browser ("Fenix") does not have extensions support and it is on an indefinite and easily ignorable backlog. It is explicitly not being worked on this quarter. At the end of this quarter is the scheduled release of Firefox 69. Unless there's…

if this is true mozilla is way more broken than i thought

callahad's comments are appreciated; GP's comment read like fact but its early days so hopefully its just fud.

Re: Firefox 68.0

#209

Post by jraph »

hu3 wrote: post #195
jraph wrote: post #128

Earlier quoted context omitted.

"Fenix MVP will not replace Fennec" (MVP meaning "Minimum Viable Product"). https://github.com/mozilla-mobile/fenix/issues/662#issuecomm... I'm sure Fennec users will not be migrated to Fenix until extensions are supported. This would be a big fuck up and Mozilla is aware of this. Linked bugs about the user agent seem irrelevant to this issue. Everything will be okay. You can sleep on both ears.

Sorry but this seems conflicting with what callahad replied above https://news.ycombinator.com/item?id=20394503 when answering "Will Preview be guaranteed to support extensions before Firefox for Android goes EOL?": > I can't make any specific commitment, but there's a lot of time between now and Firefox for Android going EOL (and we haven't committed to specific timing for that, either.) > However, we do have concre…

I am reading this differently: it seems likely that Fenix supports extension before Firefox 68 goes EOL, but they don't want to make any announcement yet (maybe, because they don't really know what is going to happen).

I agree with you however. We don't have any guarantee at this point.

Please, Mozilla: don't EOL Fennec before supporting extensions on Fenix. This would be a huge mistake. Extensions are useful beyond adblocking. Chrome not supporting extensions on mobile is not a good reason to consider that Fenix would be good enough without support of extensions. Chrome is not good enough. If Fenix is not ready early enough, please consider releasing a version 69 of Fennec and then later versions until Fenix supports extensions.

Re: Firefox 68.0

#210

Post by maccam94 »

dralley wrote: post #159
tssva wrote: post #48

Earlier quoted context omitted.

There is a known severe performance issue on MacBooks with retina screens and integrated Intel graphics which this is suppose to be the solution to. Unfortunately this doesn't seem to have driven macOS to be a priority for the rollout.

MacOS uses an absolutely decrepit version of OpenGL and a special vendor-locked graphics API (Metal) that nobody else uses. It's not surprising they get low-priority when Apple makes it a pain to do write a crossplatform app that is supported on their platform.

gfx-rs is a project to provide graphics APIs in Rust, supports Metal as a backend, and there is active work to make WebRender/Firefox work with it.

https://github.com/gfx-rs/gfx

https://github.com/szeged/webrender/issues/198

Post reply on HN