46 ms·
How you can contribute to Firefox 57 success
- ebauch 9y agofirst AMD with Ryzen and now FF. Working with nightly in the past few days and don't miss a thing. Of course not all plugins are ported yet, but ublock works already. keep up the phenomal work.
- iamnotlarry 9y agoThis includes a call for help on Photon, the "new user interface." "Since the UI is written in major parts in JavaScript and CSS and an HTML-like language called XUL, anyone with webdev skills can improve it!" I thought 57 was dumping XUL completely. Wasn't that a major point of 57?
- throwaway2048 9y agoXUL is still there, and there are no immediate plans to get rid of it. Mozilla has just decided that you dont get to use it anymore, the deadline is purely an administrative decision. Its great to see they are going to drive firefox off a cliff with yet another anti-user decision. The situation with popular extensions has improved, but there is going to be a lot of pain, especially with XUL functionality that they refuse to implement in WebExtensions. https://arewewebextensionsyet.com/ https://arewewebextensionsyet.com/
- brighteyes 9y ago> XUL is still there, and there are no immediate plans to get rid of it It's true it's still there, but I think the plan is using it less and less. No new UIs are written in it and many things have been rewritten from XUL to HTML5. Eventually it could be removed entirely.
- throwaway2048 9y agolonger term that is sensible sure, but the ecosystem is not ready for it. Its amusing to me that mozilla expects everyone else to be moved off XUL, but not their own code because it has legitimate reasons....
- angelsl 9y agoThey are moving everyone else off so they themselves can move off XUL.
- adrianN 9y agoIt is my understanding that getting rid of XUL in favor of a less peculiar way to do UI is a necessary step to improve security and performance and get rid of a lot of legacy ballast that keeps Firefox from getting better. So there are some upsides to the transition. Time will tell whether it will be a success or whether it will "drive Firefox off a cliff". I don't think you can say a priori what the result will be.
- throwaway2048 9y agoI think you can say a priori, that a major remaining reason to use firefox over chrome is about to be eliminated. Hilariously, dispite the pro-privacy stance mozilla pretends at, they want to start tracking urls visited https://news.ycombinator.com/item?id=15071492 https://news.ycombinator.com/item?id=15071492 Why keep using firefox? Because I love Mozilla so much when they clearly have zero interest in my needs as a user?
- 482794793792894 9y agoThe UI toolkit "XUL" is something different from the extension API "XUL/XPCOM". And no, it's certainly not just an administrative deadline. For now, you can still tell Firefox Nightly to install legacy extensions, the vast majority of them are just by now completely broken, because Mozilla is ripping out all of that legacy code and refactoring what's left. Here's a list of all of the things that they can get rid of: https://bugzilla.mozilla.org/show_bug.cgi?id=1347507 https://bugzilla.mozilla.org/show_bug.cgi?id=1347507
- chr1 9y agoThe question is not about "XUL functionality" specifically, XUL is just an implementation detail, and html could work in its place just as well. The question is how much the extensions can do, in the old model they could do anything firefox code could do, in WebExtensions model, they can do only very limited set of things. On one hand it is quite sad to see firefox extensions go, on the other hand the old model was a maintenance hell both for firefox developers and for addon developers, because smallest changes in firefox ui were breaking bunch of addons, and even changes in addons themselves were breaking other addons, which all had incompatibilities and had to do lots of subtle hacks to work together. I have worked on firefox addons for several years, and had to quit firefox when they started ignoring addons and investing in old addon sdk. But saying Mozilla is intentionally killing firefox is not fair the whole thing was shaky and full of hacks and would crumble by itself too. What they should do now, is splitting their ui from the engine, so that advanced users can hack on the ui and get all the benefits of old addon system without the mess. If they fail to do that brave browser with https://github.com/brave/muon https://github.com/brave/muon will take that niche.
- ChrisSD 9y agoThe eventually goal is to fully dump XUL but that's going to take time to finish. The major point of 57 is legacy addons will no longer be supported. Think about it this way: the transition away from XUL means the UI code (and more) is going to be very unstable for awhile. Thus addon authors would need to be continually rewriting their code for each update to keep up with the changes. It's better to bite the bullet now and switch to a more stable api.
- throwaway2048 9y agoThey are not transitioning away from XUL
- ksec 9y agoAre they not ? I thought that was the long term goal. https://github.com/browserhtml/browserhtml https://github.com/browserhtml/browserhtml
- ChrisSD 9y agoSource? Last I heard from Moz, XUL was considered a maintenance burden that increasingly suffers from neglect. HTML now does a comparable job, is standardised, is widely used and needs to be implemented anyway. Maintaining two interface languages doesn't make much sense in the long term.
- deleted 9y ago[deleted]
- 482794793792894 9y agoThe XUL/XPCOM extension API is a massive maintenance burden. The XUL UI toolkit is something different and while it's not either magically free of maintenance cost, it's much less of a maintenance burden than the XUL/XPCOM extension API.
- chr1 9y agoXUL is the same XUL both in extensions and in browser ui. XPCOM is another independent technology https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM. They are disabling the direct access from extensions to apis used by browser itself (that is access to XUL _and_ XPCOM), to be able to modify the browser ui without worrying about breaking extensions, with the goal to remove XUL eventually.
- TazeTSchnitzel 9y agoSurely Photon would use HTML, given it's new code?
- 482794793792894 9y agoNope. It uses XUL. It is in some parts new code, but not completely. If you were using Firefox Nightly, you could actually see them slowly changing Australis over to Photon.
- 482794793792894 9y agoIt's dumping the so-called "XUL/XPCOM extensions", so that's an extension API. The UI toolkit XUL, they'll continue to use. There are some long-term investigations into using HTML/JS/CSS for the UI [1], but for the moment, the performance difference is still too much. [1]: https://github.com/browserhtml/browserhtml https://github.com/browserhtml/browserhtml
- btrask 9y agoWhy is HTML slower than XUL? I thought XUL was pretty much just a weird version of HTML, possibly with more native toolkit support. Is it because XUL is being used from C++ rather than JS? (I checked the browser.html issue tracker but most of their perf bugs seemed to be resolved.)
- MBCook 9y agoIt may also be that XUL is more restrictive or less forgiving. By not having to handle as many edge cases they can skip a lot of code and speed things up. This is just a guess on my part.
- Yoric 9y agoI remember, for instance, that XUL was highly optimized to not create DOM nodes for huge/infinite lists/trees/... Last time I heard about someone attempting to implement these optimizations with comparable APIs in HTML5, the results were ok, but not nearly as good. That was a few years ago, results may be obsolete, of course.
- fabrice_d 9y agoHa, the xul tree and it's virtual view... Someone (working now at Apple) wrote a super fast list component in HTML for Firefox OS so this can definitely be done.
- hendersoon 9y agoNot sure which APIs you're referring to, but the Vivaldi browser UI is largely rendered in HTML5 and its performance feels native to me.
- mintplant 9y agoThe Browser Architecture team at Mozilla [0] is investigating stripping XUL(/XBL) out of Firefox, among other things, but it's more complex than you might expect. [0] https://github.com/mozilla/firefox-browser-architecture https://github.com/mozilla/firefox-browser-architecture
- r3bl 9y agoAnd yet, no Yubikey support, that they were hoping will land in November in stable.
- foobar20198 9y agoSo does that mean Mozilla don't use 2FA?
- deleted 9y ago[deleted]
- mintplant 9y ago2FA is actually globally enforced for all internal Mozilla accounts, IIRC---it's just not done over U2F. I'm not sure whether the details are public so I can't elaborate further.
- stinkytaco 9y agoI had good luck with the add-on [1], but it looks like it will break in 57. [1]: https://addons.mozilla.org/en-US/firefox/addon/u2f-support-add-on/ https://addons.mozilla.org/en-US/firefox/addon/u2f-support-a...
- r3bl 9y agoSo, one stable release without something like a two-factor authentication method. Since the addon will break and no official support will be released on time, there's no other choice but to use Chrome/Chromium to use Yubikeys.
- majewsky 9y agoOr, you know, just use the ESR release for a few weeks.
- zbraniecki 9y agoThe plan is to support it in 58: https://github.com/prefiks/u2f4moz/issues/59#issuecomment-325768286 https://github.com/prefiks/u2f4moz/issues/59#issuecomment-32...
- TheAceOfHearts 9y agoIt has been a while since I last tried compiling Firefox, so I don't know if things have improved. In some of my previous setup and build attempts I ended up giving up out of frustration. Just updating the docs would probably be of huge help to many users.
- digi_owl 9y agoMore and more it feels that self-compiling is not a considered usage for large projects. Instead if you compile at all, you do so as part of a distro maintenance team. And thus should be on all the relevant mailing lists and irc channels, and keeping notes. At least that is how it feels to me after having spent some years using a distro that is a fair bit more hands on than most.
- JosephLark 9y agoWhat about development? You need to be able to compile to test feature implementation and bug fixes.
- digi_owl 9y agoNightly automated builds...
- TheAceOfHearts 9y agoThis is definitely relatable. I've lost interest in many projects after wasting hours trying to get things to compile. The worst offender I've encountered has been android. The initial checkout is like +100GB, and it has incredibly poor fault tolerance. Based on my experience, it fails regularly at random points, requiring you to re-fetch everything. Despite multi-day efforts, I've never managed to build a ROM for my Nexus 5X or Pixel.
- JosephLark 9y agoI'll add a +1 to this very issue. I likewise am not sure if it's still the case, but a few years ago I was looking into contributing some ES2015 implementations to the FF JS engine but couldn't get Firefox to compile based on the docs. I get that software development involves some amount of grit to grind out a problem and solve it, but to have to do so right at the beginning of possibly contributing to an open source project was asking just a bit too much of my free time and I bailed and have never made the attempt again.
- ygaf 9y agoAnd they need help in collecting theoretically anonymous data: https://news.ycombinator.com/item?id=15071492 https://news.ycombinator.com/item?id=15071492
- zbraniecki 9y agoWe also need help in making it practically anonymous :)
- kuschku 9y agoAnd you need to submit complaints to your local data privacy official about this planned data collection which is not opt-in (and therefore violates the privacy laws). If you live in the EU, submit a complaint to your local data privacy official, in Germany those are the Landesdatenschutzbauftragten and Bundesdatenschutzbeauftragten, for example, you can find the ones for Schleswig-Holstein here: https://www.datenschutzzentrum.de/impressum/ https://www.datenschutzzentrum.de/impressum/. Submit a complaint today, so that a legal process against Mozilla can happen before they implement this.
- sgift 9y agoSection 28, (6) of the BDSG (German Federal Data Protection Act): (6) The collection, processing and use of special types of personal data (Section 3 (9)) for own commercial purposes shall be admissible when the data subject has not consented in accordance with Section 4a (3) if (...) 4. this is necessary for the purposes of scientific research, where the scientific interest in carrying out the research project substantially outweighs the data subject's interest in excluding collection, processing and use and the purpose of the research cannot be achieved in any other way or would otherwise necessitate disproportionate effort. --- https://www.gesetze-im-internet.de/englisch_bdsg/englisch_bdsg.html#p0383 https://www.gesetze-im-internet.de/englisch_bdsg/englisch_bd... --- IANAL. Everyone may draw their own conclusions.
- kuschku 9y agoYou quoted: > The collection, processing and use of special types of personal data (Section 3 (9)) BDSG Section 3 (9) says: > (9) “Special categories of personal data” means information on a person’s racial or ethnic origin, political opinions, religious or philosophical convictions, union membership, health or sex life. This exception does not apply to behaviourial tracking, such as the list of the visited domains. This is not legal advice, I am not a lawyer.
- fiatjaf 9y agoSo the devtools were rewritten from scratch? Are they fast now? If they are I'll jump in.
- Manishearth 9y agoIME pretty fast. You can even contribute to them without a Firefox clone, they're an entirely separate repo that contains a webpage that can be run in both Firefox or Chrome as a regular website and used to debug both. It's fun!
- starik36 9y agoI would say the FF devtools are almost there. And I prefer using them. But there are small things here and there and keep bringing me back to Chrome. Example of a network timeline. Chrome: https://i.imgur.com/16ZLENd.png https://i.imgur.com/16ZLENd.png Firefox: https://i.imgur.com/1j0NZcd.png https://i.imgur.com/1j0NZcd.png I get a better representation of the timeline waterfall in Chrome. Like I said, the tools are almost there.
- foobar20198 9y agoIt seems a bit awkward to me when Mozilla keep asking for contributors. They're profiting from Firefox (via the huge search engine deal), it's in really poor taste when such organisations then beg for contributors. They have enough money to employ people to keep their product going... Kinda the same with e.g. Facebook's open source projects, although I guess there are worse places to contribute (and FB's projects might actually be useful for other companies work - hence contributing isn't a complete waste of time). My only exception would be scratching my own itches, but here they're asking for help with company goals.
- imtringued 9y agoCompanies like Facebook publish their libraries so they can hire people who are already familiar with the libraries they internally use. As an outsider you can't be an expert in <company internal library> if you don't even whether it exists.
- Sylos 9y agoMozilla is a non-profit organization. Any money that they make, they have to reinvest into Firefox or other Mozilla projects. There's not some guy getting rich from you helping them out. All the help that you invest will eventually fall through to users in some way.
- chappi42 9y agoThey could be more frugal. And imo a lot of money has been wasted for bad projects. Rust is very nice though.
- foobar20198 9y agoTo be completely fair: many projects at many companies turn out to be failures. Rust could've been bad and Firefox OS could have ended up ruling the world, and suddenly your comment would look very different. There's just a fundamental risk in projects, and viability often only becomes later in hindsight. (Most other companies failures just happen to be a lot less visible since they're not developing in the open.)
- ivanstojic 9y agoBack in ~2015, there were several Firefox developers who visited a local hacklab where I used to hang out. I was aware of a bug in the current version of FX at that time, and I knew how to fix it. I wanted to get their help to create a patch for the bug and get it submitted. After about two hours of trying, we were unable to produce a working build from a tagged release point in their version control - even before applying any changes. I'm hoping the new tooling works better.
- hsivonen 9y agoI'm curious: Which operating system? The Linux x86_64 build experience has worked very well on Ubuntu for many years. These days you don't even need to copy and paste the apt incantations: ./mach bootstrap takes care of that.
- ivanstojic 9y agoIt was on a Mac, which I admit probably isn't where the core of development lies.
- digi_owl 9y agoOddly my impression is that their focus is more on Mac and Windows than on Linux. I swear that whenever i see them presenting something, it is invariably done using a Mac.
- fabrice_d 9y agoMany gecko/firefox devs work on Macs, so it is very surprising to hear that, unless your are running a somewhat old and unsupported version of MacOS (you need 10.7 according to https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Mac_OS_X_Prerequisites https://developer.mozilla.org/en-US/docs/Mozilla/Developer_g...).
- spaceseaman 9y agoYou should download the code today and try to build. https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build/Linux_and_MacOS_build_preparation https://developer.mozilla.org/en-US/docs/Mozilla/Developer_g... It's just a ./mach build after checking out the code and running the bootstrap script.
- heardy 9y agoI just updated FF Nightly on Android and the new Photon UI is very big, very white and very obtrusive feeling in comparison to before I updated. I've got a pretty small android phone, I'm sure it looks better on the phablets of the world, but I ask for a dark UI option and small screen footprint please. Edit: Found some images http://www.androidpolice.com/2017/08/08/mozillas-new-photon-ui-arrives-firefox-nightly-android/ http://www.androidpolice.com/2017/08/08/mozillas-new-photon-... I just noticed, it recolors my system stsusbar too. So, it's white on white while FF is open. Everywhere else it's black.
- vanderZwan 9y agoI think it uses the same number of pixels though, so the only issue would be a dark UI option (which I agree would be nice, especially in the evening)
- majewsky 9y agoThe new look screams "generic". You can say what you want about the old design, but you could always tell that someone was using FF Mobile because of the distinct black rounded background on the buttons. The new design looks like literally every other mobile browser in existence.
- mintplant 9y agoOn the other hand, the most comment complaint I've seen in the wild about FF for Android is "the UI looks weird / doesn't fit in with the rest of Android". You can't please everyone.
- boyce 9y agoI've been doing more browsing in private mode because of the dark bars Do hope there's an option to change it soon
- klondike_ 9y agoThis design is indistinguishable from any other mobile browser. The old design was a bit dated but it was distinct at least.
- cmurf 9y agoIt'd be easier to test and keep current with what Mozilla wants tested if they had a delta update for the nightly rather than a monolithic binary. For example if they jumped on board with delivering a flatpak version.
- zbraniecki 9y agoIf you download nightly from nightly.mozilla.org, we'll keep offering you delta binary updates twice per day! :)
- kirillkh 9y agoDear Mozilla developers! I've been using Firefox since v1.0. And I want you to know that by ditching the old plugin architecture you are alienating your faithful users, myself included. I'm sorry, but I decided to stick with Firefox 55 for now, possibly switching to Palemoon later. I need my old extensions to work: Status4Evar, EdgeWise and Classic Theme Restorer. I can't stand the current FF UI and I will not give up on this.
- 51Cards 9y agoOne more voice for the above. I will be stopping at Firefox 56 until I decide what works best for me. I rely on several plugins daily that are about to be made obsolete. Likewise I revert Firefox back to a very classic UI interface that is very compact and familiar. I have avoided Chrome all these years because I can't stand its UI. Now I'm also about to loose the ability to make FF feel familiar along with many of my required productivity add-ons. I'll ride out FF 56 until I decide where to go next but honestly the many times in the past it has felt FF has ignored the requests of long term users, coupled with lack of differentiation from Chrome, I'm not sure I have much reason to stick around. Kudos to the team for all the hard work improving the FF core. But you're about to abandon that which kept long term users like myself here through all those rough years. Makes me sad.
- romanovcode 9y agoI don't agree. Yes it's a change but it serves a good purpose - to standardize the extension development and making sure that 1 extension can be running on multiples browsers e.g. Firefox, Opera, Edge, etc..
- drdaeman 9y agoWebExtensions is the lowest common denominator. Yes, it's a good purpose to have a standard base. It's bad, though, that nothing besides the blessed parts are officially customizable anymore. Previously, extensions had messed up with anything they wanted (they could override most of the browser's core). That had allowed third parties to do incredible things that weren't ever considered by the browser developers. With WEs, though, the only things that browser developers had specifically thought about are possible. All for user's convenience, so they can switch to Chrome, Edge or Opera.
- Teichopsia 9y agoTLDR; could someone point me to a tutorial or an explanation on how to properly install FF, update & save the open tabs without making bookmarks (that last point is and edge case we can skip if it's difficult), and having the current icon, on a nix system that has explanations for 5 year olds? I would love to help but being an amateur I've encountered a few pain points, unless the issue is my search skills are lacking. A few days ago I finally updated my Firefox version on Debian 9 to the developer version 56 (previous 54). The problem has been finding documentation on both the Debian and Mozilla websites on how to do it the right way. Found a decent tutorial, made a back up, installed and my machine is working much better. It is old and got little memory :) Then FF said there was an update. I got stumped. From what I could find FF sync has a limit of X bytes. I ended up looking into making a web extension but that's going to take me some time. It seems I could save the open tabs using Tabs.tab from the API, maybe. Sorry, I digress. In short, how can I have two FF versions on at the same time, different directories obviously, with their respective icons, while manually updating them? I guess it would be to delete all the files in the dir, unpacking, and call it a day? Still need help with the two versions though. If you read all of this, thank you.
- klondike_ 9y agoI'm not sure exactly what you're asking, but try just using the same profile for both installs. It contains all the information about your browsing session including tabs, bookmarks, extensions, cookies, etc. https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles https://support.mozilla.org/en-US/kb/profile-manager-create-...
- 616c 9y agoHis point is concurrent usage of one profile. FF does not support this. Queue the FF is not tread safe jokes (and only that, not a flame). OP: you can use Firefox Sync. There is a cloud version by Mozilla but also a WSGI app you could host. I know it is not a 100% solution, but what was recommended to me when I asked during FF alpha and beta testing with stable way back when.
- 9y ago
- vortico 9y agoIt's really sad. I love Firefox, but I think when 57 releases, it'll mark the beginning of the end before everyone switches to Chromium, when they realize it's easier to switch browsers than to find alternatives for all their extensions due to Mozilla's way-too-early deprecation of the existing extension API before many developers are able to switch APIs. Many extensions simply cannot be switched, like Vimperator, due to lack of features in the WebExtensions API or the complexity of the change. Other extensions were developed as one-off projects, like "Google Similar Images" or "Remove Google Redirect in Google Results", so their developers are not around anymore to update to WebExtensions. That and Mozilla's search for "anonymized personal data" kill the benefits of using Firefox in the first place, which for most people is to avoid using Chrome/Chromium, made by a conglomerate advertisement company. Just last week, I updated to 56 beta and despite disabling Pocket in my about:config, advertisements for news companies (Wired, etc) were displayed thanks to Pocket's "popular news articles" section in my previously blank New Tab page! Even Chrome does not force bundled software like Pocket, despite their stronger incentives for doing so. I downloaded nightly 57 and it gave me a preview of how bad the extension situation really is. It's like a forced downgrade to a completely different browser, so why not switch to something entirely different at that point? This is what I'll be forced to do, after certificates expire in a few years in the then-out-of-date stable 56 distribution.
- kosinus 9y agoI'm really not sure and curious how much extensions are actually used in practice. Personally, I use Chrome with 1password, that's it. Extensions scare me. They're a huge potential invasion of privacy, especially with recent hijackings of Chrome extensions in the store. I'm also more confident that Mozilla will always listen to users, and give us the necessary opt-outs. I really don't trust Google as much.
- vortico 9y agohttps://blog.mozilla.org/addons/2011/06/21/firefox-4-add-on-users/ https://blog.mozilla.org/addons/2011/06/21/firefox-4-add-on-... Here's an article from 2011 claiming that 85% of Firefox users have extensions installed and will thus be bothered by the change, and on average, users have 5 addons installed. It is my gut estimate that half of these addons have no replacement or a worse replacement. As for the opt outs, this may be true for most things, but I am not able to opt entirely out of Pocket's "Recommended by Pocket" trending adverts, nor am I able to turn off Firefox's addon signing requirement to develop or try new addons from GitHub, unless I download a tweaked build version of Firefox.
- hendersoon 9y agoDue to breaking XUL extensions with no adequate replacements, mouse gestures in particular, I recently switched from Firefox to Vivaldi. After thirteen loyal years with Firefox as my primary browser they finally forced me away. Bye, Mozilla.
- sgift 9y agohttps://addons.mozilla.org/en-US/firefox/addon/foxy-gestures/ https://addons.mozilla.org/en-US/firefox/addon/foxy-gestures... Works great on my nightly installation, but have fun with Vivaldi.
- darrmit 9y agoI just tried the Nightly on Windows and I'm very impressed. Much faster and better looking. Long time Firefox user and have been dreading the extensions going away, but it looks like Nightly has resolved some of the problems I was using extensions for (i.e. duplicate tab context menu) and I know some of the more prominent extensions (like NoScript) are being worked on.
- jorvi 9y agojust tried it on macOS and I have to agree it feels very well made. Some issues though: instead of going for 'native', they still seem to feel like Firefox is a little planet of its own. It doesn't use macOS-style menus, nor transparency. Not that Chrome uses all macOS style elements, but it at least feels like it has had some effort put into making it feel at home on macOS. There's also some weird defaults / ignorance of convention: every browser launches a private window with cmd+shift+n, Firefox uses cmd+shift+p. There's still a separate search field next to an URL&search field. Probably a few more that I missed.
- bzbarsky 9y agoIn Firefox, cmd+shift+n is "undo close window" and has been for a very long time. Possibly even predating private browsing mode... Other browsers don't have to have "undo close window" as a feature at all, so had the shortcut free for private browsing.
- zbraniecki 9y agoGlad you like it! On the issues - what you listed is the eternal dilemma of cross-platform software. Balancing cross-platform behavior vs. platform-compliance. There are choices that are just "Firefox-specific" like the shortcut to open private window. Other items like "Gecko menus vs MacOS menus" are tradeoffs of productivity. Having one set of menus for all platforms is easier to maintain than separate for each. Those choices are hard to make perfect. I've been recently fixing the drop-down menu lists styling [0] to allow websites to style some of it, while keeping it looking native when they don't. It's pretty tricky to get it right :) [0] https://bugzilla.mozilla.org/show_bug.cgi?id=1386015 https://bugzilla.mozilla.org/show_bug.cgi?id=1386015
- fiatjaf 9y agoIs OpenSearch support planned? Or is there an extension that does implement it?
- fiatjaf 9y agoOh, nevermind, there's a different kind of OpenSearch support that seems very nice. I think I'll stay with Firefox this time.
- fiatjaf 9y agoDoes anyone know how can I stop the menu from vanishing (very slowly) and reappearing when I hover the top of the window? I just want it to stay there.
- JBiserkov 9y agoMost comments here seem to be the result of an "How you can complain about Firefox 57" article posted somewhere else.
- saghul 9y agoLovely blog post. Well written, thorough and clear. Getting people involved in a large project is not an easy feat, and I think this may open the eyes of people not knowing were to start. Well done!
- Markoff 9y agoI might give it a try again as usual every year at least once, but I always end up with conclusion Firefox is unresponsive, freezing and has problems with rendering compared to smooth experience with Chrome. I would be very happy to ditch app from Google, but if it's crashing, freezing and has basic problems I am not gonna waste time with firefox, Chrome just works. So I hope I will be surprised and Firefox finally made some revolutionary changes. Btw. it's even worse on Android, you will hardly find slower browser + there is no pull down to refresh page which is showstopper for me and even with plugins there was no way to implement it.
- lucb1e 9y agoHit the download button for nightly, only to start reading the comments here and realizing that a bunch of addons will stop working. Checking my list, FireGestures will stop working, Self-Destructing Cookies apparently already stopped working this version (broke localStorage deletion), and a more obscure one (QuickJava) is also legacy. The latter is the only one I could find that adds easy on/off toggles for Javascript, CSS, Flash and Proxy. They want to receive telemetry to see how people use nightly? Well, here's my datapoint: can't use it altogether. I might as well switch to MSIE as update to 57.
- zbraniecki 9y agoThis sheet may help you find replacements: https://docs.google.com/spreadsheets/d/1TFcEXMcKrwoIAECIVyBU0GPoSmRqZ7A0VBvqeKYVSww/edit#gid=0 https://docs.google.com/spreadsheets/d/1TFcEXMcKrwoIAECIVyBU... FireGestures -> https://addons.mozilla.org/en-US/firefox/addon/foxy-gestures/ https://addons.mozilla.org/en-US/firefox/addon/foxy-gestures... SDC -> https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/ https://addons.mozilla.org/en-US/firefox/addon/cookie-autode... It'll take a bit for the new generation of extensions to fully replace the old one, but it's happening.
- tw04 9y agoDownthemall was the only reason I was still using firefox. The "replacements" are extremely poor imitations, disappointing but I guess all good things must come to an end.
- rjzzleep 9y agoI'm not sure they will. Vimperator etc. has a lot of dependencies some of which will never come to be. But the parts that could, like a proper keyboard api hasn't even been reviewed for months. The community complained about the lack of apis, they made a webextension experiment, which is apparently the way you ask for api extensions and it's pretty much just being ignored(the thread is 2 years old [1][2]). The customization thing mentioned also applies since the plugin creates a custom status bar and hides all sorts of other stuff. I'm not sure what browser I'm going to use to be honest. All the hotkey browsers are buggy as hell since they use qtwebkit, webkitgtk, qt-webengine and whatnot. Chrome has extensions like cvim which sort of work, but they suffer from issues like not being able to properly hook keys and properly notify the user about the state you're in making me frequently make mistakes on what I want to do. As the sibling said a poor imitation of what was possible before. If firefox just immitates chrome, what's the point in having it? How about trying to eat some of IE's lunch by making enterprise customization a first class citizen? But then again not sure if that matters. And yes I'm aware of GPO[3], but calling that first class citizen is disingenuous at best. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 [2] https://github.com/Koushien/keyboard-shortcut-api https://github.com/Koushien/keyboard-shortcut-api [3] https://addons.mozilla.org/en-us/firefox/addon/gpo-for-firefox/ https://addons.mozilla.org/en-us/firefox/addon/gpo-for-firef...
- electrotype 9y agoPlease Firefox developers : always keep in mind that power users are loyal to Firefox for some specific reasons. One of those reasons is that Firefox is, by far, the browser with the most customizable interface. The "Customize..." feature is why I personally stick to Firefox : http://i.imgur.com/AH1ahF3.jpg http://i.imgur.com/AH1ahF3.jpg I really don't care which browser is #1 in speed tests. I don't care about integrations with social networks. I simply want a browser that I can configure the way I want! Another suggestion : when you change something, even if you are 100% sure everybody will like it, please at least leave an "about:config" option that can revert that modification. Sadly, I realized that, when Firefox is updated, I'm not trilled anymore to see what new features are included, I'm instead anxious to see what has been changed/removed!
- chrisseaton 9y agoWhy do you want to customise so much? I know there are people like you but maybe like the Firefox developers I don't understand it. I use software as it comes. I almost never change any options. I don't even change my desktop wallpaper. I think making developers add options for everything creates bloat. Just use the defaults!
- nkkollaw 9y ago> Just use the defaults! Just customize!
- chrisseaton 9y agoAdding support for customisation has a cost - more code, more things to test. If people just used defaults we could have simpler code, shipped more quickly, with fewer bugs.
- nkkollaw 9y agoSo? Not supporting images or JavaScript would simplify things as well...
- nkkollaw 9y agoWow. What a difference. Congratulations. This is definitely a huge step forward. The UI finally looks as good as the other guys, and it's fast, too! If you had finally figured out that private mode's UI is too similar to the normal one, too, I'd even be amazed (let me help you: make the address bar and tabs dark instead of light).
- amingilani 9y agoFor people that need legacy addons like I needed LastPass, go to about:config and toggle extensions.legacy.enabled to true
- rnhmjoj 9y agoI won't be happy if it were to fail but certainly I won't despair either. I don't want amazing performance improvements at the cost of huge functionality losses. This update is simple a regression: almost every add-on I have been using will stop working and has a stupidly limited or no replacement at all. There will really be no reason for me to still use Firefox over any other browser now. The only option seems to switch to the ESR version, at least for a while it will work.
- tradesmanhelix 9y agoThis sums up my feelings re. Firefox 57: https://www.change.org/p/mozilla-save-mozilla-firefox-s-best-feature https://www.change.org/p/mozilla-save-mozilla-firefox-s-best.... Sorry Mozilla - for the reasons expressed above, 56 will be the last version of your browser I'm able to effectively use given the demands of my browser workflow. If my use-case no longer fits your business case, then we will part ways. Currently, it looks like my best options are either Waterfox (with its pledge of continued XUL extension support), or Vivaldi.
- Sylos 9y agoVivaldi has less powerful extensions than Firefox 57. I can't imagine Waterfox or Pale Moon being able to keep XUL extensions alive for much longer. It was a major maintenance burden for Mozilla, so it's pretty much an impossible task for the comparatively tiny developer teams behind those. Having said that, Firefox 52 ESR is still supported until June 26, 2018. So, you could use that. And the Waterfox + Pale Moon devs could base themselves on that until its EOL.
- tradesmanhelix 9y agoVivaldi provides arguably the most customizable UI of any browser out of the box (see: ability to move tabs to any side of the screen), plus their culture seems to me to be all about customization and providing options. I like that. Firefox ESR is pointless - it's just delaying the inevitable. I tried Midori, but it runs poorly on KDE. Palemoon is pretty bad - I tried it and it doesn't properly support existing XUL extensions that work fine in Firefox, so it's a no-go in my book. Waterfox, on the other hand, is fast, works exactly like Firefox, and is at least willing to give continued XUL support a shot. So, it's Vivaldi or Waterfox as best I can figure at this point.
- pix64 9y agoMozilla can contribute to Firefox 57's success by finishing all the missing WebExtensions APIs. So many extensions are going to be impossible to recreate.
- zbraniecki 9y agoHelp us! Write patches to dependencies of this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1215059 https://bugzilla.mozilla.org/show_bug.cgi?id=1215059
- kirillkh 9y agoThanks for that link, now I can clearly see that from the power-user perspective WebExtensions is a dead-end. If you look at the RESOLVED WONTFIX issues linked in that bug, you will find a lot of them are rejected based on political reasons. For example: https://bugzilla.mozilla.org/show_bug.cgi?id=1246706 https://bugzilla.mozilla.org/show_bug.cgi?id=1246706 Listen, I don't care whether features that I need don't fit the WebExtensions security model or whether they are confusing to a clueless user. If you can't support these features as part of WebExtensions, please design a separate set of APIs. Fine with me if you market extensions targeting these lower-level APIs as "dangerous, use at your own risk".
- Ar-Curunir 9y agoTo counter all the negativity in the comments: I've been exclusively nightly-only for a year now, and I've only seen improvements. Most addons I use have replacements/WebExt versions, and the UI and performance are much better.
- megous 9y agoIt would be nice if I didn't have to abandon my privacy - reveal my personal extensions to some third party server - in order to use my own extensions without too much hassle. Now, I have to patch omni.ja every single time I get update to Firefox from Arch Linux, to disable signature verification. I can automate it a bit, although it's not a robust solution, because I'm patching some JS code that can change at any time. Beta is not an option, because I don't want it for regular use and it is not in Arch Linux repositories anyway, so I can't get it either. I don't get it. It's still possible to disable signature verification with little effort (one line change) programmatically from outside of Firefox, yet power users have to jump through stupid hoops in order to continue using their browser the way they want. I wish fight against malware/malicious extensions was not also inconveniencing power users.
- sanbor 9y agoI'm still surprised that they're spending time in a VR API while lacking many basic things like print preview functionality. Also In the last year every time I give firefox a try they dev tools are very buggy. Instead of improving the dev tools they waste time in Firefox for devs (which is funny because as web developer I want to develop in the same browser that my users, but instead Firefox for devs is a version ahead, so once I thought my website worked okay in Firefox but it really didn't because it didn't work well in the stable version of Firefox). I feel like the browser is getting faster though which is good. I also like Mozilla as an organization but I feel that they still lack the direction and focus to make Firefox better than Chrome. To be fair, I think Firefox for Android is better than Chrome for Android. And Firefox Focus it's neat too!
- bzbarsky 9y agoUm... Firefox has print preview and has had it for a long time. It's not enabled on Mac, where there is a native print preview available from the print dialog: you can fiddle with the settings, then "Open PDF in Preview". Is it possible you're on Mac?
- Endy 9y agoThere's an XUL print preview plugin. :-)
- sanbor 9y agoGood to know, thanks! I'm just still astonish that after so many years they haven't implemented that functionality. I don't print stuff all the time but sometimes you want to save things as pdf and fiddle a little bit margins/etc.
- Endy 9y agoHow can we best contribute to the total removal and scrapping of WebExtensions in favor of a more robust XUL development environment? How can we contribute to Firefox not becoming another meaningless Chrome clone like Opera or Vivaldi? Because that's what I think would be the best success of Firefox, long-term.
- zbraniecki 9y agoI know you're sarcastic, but I'll try to answer anyway :) > How can we best contribute to the total removal and scrapping of WebExtensions in favor of a more robust XUL development environment? I don't know if that would be possible. We're moving a lot of XUL around these days and we'll be moving even more, hopefully to HTML soon. You'd have to gain trust in the community as a reliable person willing to maintain and keep relentlessly updating your addons APIs as the UI of Firefox moves underneath it. > How can we contribute to Firefox not becoming another meaningless Chrome clone like Opera or Vivaldi? I assume by "another clone" you refer to the fact that we're switching to WebExtensions which is a system shared with other browsers. In that case, pick any of the bugs here: https://bugzilla.mozilla.org/show_bug.cgi?id=1215059 https://bugzilla.mozilla.org/show_bug.cgi?id=1215059 and help us extend the API surface to support more features :) > Because that's what I think would be the best success of Firefox, long-term. I agree! We already support more APIs in WebExtensions than any other engine as far as I know. And we only started.
- Endy 9y agoI'll be blunt. When you break compatibility with Classic Theme Restorer, Status-4-Evar, and QuickNote, I'm switching over, 100%, to Pale Moon. Between Australis and WebExtensions, Firefox has been moving farther and farther away from a browser I want to use. It's really getting to a point where I'm happier using Lynx.
- dingo_bat 9y ago57 nightly feels extremely snappy. Scrolling is no longer janky. The theme is good and sensible (at least on Windows). I am seriously going to try to ditch chrome for this. Yay! The old Firefox is back!
- yakult 9y agoSure, we CAN contribute. But what's in it for us? Are we going to get a browser that caters to our own needs? No, evidently power users are no longer the target demographic. Are we going to make a browser that we can recommend to our nontechie friends? No, I don't trust them to navigate all the opt-outs and dark patterns around your telemetry. I don't even trust myself to never misclick. Is contributing going to win us goodwill from our collegues? No, you've alienated them too. Is this about ideology, then? Are we building a browser for a better world? ..it would be much more convincing if you guys didn't fire your CEO over political speech. And that's where we're at right now. Maybe the 97% or whatever non-addon-using demographic in your telemetry data will make up the shortfall in contributions.
- mwill 9y agoMozilla has lost any good will they had with me, I'm actually dropping Firefox this year. The entire reason I switched to it was tab groups, which isn't getting ported over, so I'll be switching back to Chrome.
- yoasif_ 9y agoSimplified Tab Groups is being ported to WE: https://addons.mozilla.org/en-US/firefox/addon/tab-groups/ https://addons.mozilla.org/en-US/firefox/addon/tab-groups/ https://github.com/denschub/firefox-tabgroups/issues/60 https://github.com/denschub/firefox-tabgroups/issues/60
- Karunamon 9y agoSo I downloaded Nightly on a lark. 4 addons disabled, with a link to this page: https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing?as=u&utm_source=inproduct https://support.mozilla.org/en-US/kb/firefox-add-technology-... >You can still personalize Firefox with add-ons the same way you do now, except they won’t break in new Firefox releases. This is a bald faced fucking lie. And I don't mean that in the "sorta misleading" sense, I mean that somebody wrote something that they knew was false and 'outta be slapped for it. 57 is getting pushed out the door with missing functionality, and that is an absolute fact. You absolutely "can not still personalize Firefox the same way you do now", because you're taking that away from everyone without having the replacements ready! I can sorta understand the reason to kill XUL/XPCOM, but what I can't understand is this desire to drop it on the world come November before all the bits are in place yet. Guys, Firefox isn't going to turn into a pumpkin if you let it cook for another few months. On another note, all companies have a resource that they may not be aware of. It's called "good will". Mozilla is burning prodigious amounts of theirs: * Between the CEO drama, * the UI rewrite that was apparently received so badly it's getting reverted 4 years later * the forced addon signing, * the telemetry dark patterns, * the forced addon breakage... * the junk like Pocket, Hello, and VR APIs recieving nontrivial amounts of developer attention while stuff people actually use like print preview and SSL is either ignored or have years old debilitating bugs Combined with the demonstrated "fuck you, we know better than you" attitude that permeated all of these decisions (I really think Mozilla and GNOME are going to wind up under the same umbrella at some point)... And what to show for it? Pissed off users, and an also-ran niche browser with almost no tangible competitive advantage (and in fact, a mounting number of disadvantages) I've got no faith in this company anymore. Eventually, there is going to be a "Mozilla foundation shutting down" topic at the top of this site, and the people making the decisions are going to be completely blindsided as to why.
- frik 9y agoThank you, good summarization of the unfortunate drama around Mozilla. What ever is going on in their management, they give a shit about the Firefox and Thunderbird community. The last 5 years they did so many stupid things. It's time to close Mozilla corp and turn it back to a real open source community project. It's time to fork, like Firefox forked of Mozilla Suite. I have no faith that Mozilla going anywhere, in a few months we will read a post mortem of how the managed to loose 30% world wide browser market share in 2 years.
- deleted 9y ago[deleted]
- JohnTHaller 9y agoYou can grab a copy of Firefox 57 Nightly in portable form so it won't affect any local stuff from PortableApps.com here: https://portableapps.com/apps/internet/firefox-portable-nightly https://portableapps.com/apps/internet/firefox-portable-nigh... It's a great way to test out the features in a lower risk fashion. You can do the same with Beta, Dev, and ESR channels as well.
- Grue3 9y agoTwo words: Tab groups.
- yoasif_ 9y agoSimplified Tab Groups is being ported to WE: https://addons.mozilla.org/en-US/firefox/addon/tab-groups/ https://addons.mozilla.org/en-US/firefox/addon/tab-groups/ https://github.com/denschub/firefox-tabgroups/issues/60 https://github.com/denschub/firefox-tabgroups/issues/60
- AsyncAwait 9y agoReading the comments, I get that many users are upset about the XUL extension APIs being dropped, but what I don't get is that many of them plan to switch to Chrome. a. You're getting a less powerful set of APIs in Chrome than in Firefox, even with WebExtensions being used by both. b. You're supporting a browser by a major corporation that is already number one anyway and has a IE-style chokehold on the web, giving them even more power is not the best solution, helping Mozilla make the new APIs as close in power to the old ones would be a better alternative in my opinion. Again, it's everybody's personal choice and am not saying what anyone should be doing, just found it curious that many consider switching to WebKit/Blink to be the solution, where they won't get more power and give Mozilla even less of a say in terms of web standards and just having a decent alternative to WebKit.
- WCityMike 9y agoHonestly, I can't believe how tone-deaf the entire organization has been on this. I know that's not popular to hear, but I keep seeing people tell them, over and over again, that the loss of customizability and functionality -- and the repeated elimination and crafting of design and UX to bring it into a mirror-image of Chrome UX -- is not what their users want. Yet every person on the Firefox team that I've seen actually respond has insisted, in the face of this overwhelming feedback, that it's necessary and desirable. That's fine, but I think they're going to get a rude awakening afterwards. It'll be wonderful if I have to eat my words on this, but I don't think so. Firefox is really just becoming a mirror image of Chrome, and if they're not, then they're not doing a great job on understanding why people valued -- and, yes, that's purposefully past-tense -- Firefox, and they're doing a very poor job on distinguishing why people should choose to stay with Firefox over Chrome.