bo, thx, but i dont need further help for firefox 57 - i dropped it for now because webextension api for my needs is "...not ready" when i upload several converted extension to sign. trust me, i have testet more than 4 and not only from the first side, either "newest" or alphabetical. the result list is fake. in special when v42 as minimal version is set - v42 never knew about webextension api -> never possible. and as i wrote very rare hybrids only. ps downgrade from v55 will definitely lose all favicons, and there are some other changes which are not downgrade usable. glad who has a backup from v54.
This might be useful... https://docs.google.com/spreadsheets/d/1TFcEXMcKrwoIAECIVyBU0GPoSmRqZ7A0VBvqeKYVSww/edit#gid=0
I mentioned elsewhere that quite a list of APIs will be added to FF to allow for features which were only possible with legacy add-ons. Here's one example: There is a 7 year old issue for Chromium about adding an API to enable localStorage management for add-ons. 7 years old - but no solution in sight! Now compare this with FF: A patch for a corresponding bug is available and will probably be implemented before long. This will enable webextensions like Cookie AutoDelete (which is inspired by Self-Destructing Cookies) to also remove localStorage by host. So, yes - some extensions will never be converted. But once those APIs are ready many more will. And above example suggests that Mozilla is much more responsive than Google in accepting such requests.
FWIW, right now I'm using/testing the following add-ons (all of them are pure webextensions) with FF57 Nightly: Code: Canvas Defender 1.1.0 true @canvas-shadow Cookie AutoDelete 1.4.3 true CookieAutoDelete@kennydo.com Dict.cc Übersetzung 5.1 true searchdictcc@roughael Don't touch my tabs! (rel=noopener) 1.0 true {6b938c0c-fc53-4f27-805f-619778631082} Duplicate tab 1.3 true {54fa1e34-a0ad-4526-a81b-b06139adf332} FoxyTab 2.2 true foxytab@eros.man Open Tabs Next to Current 2.0.8 true opentabsnexttocurrent@sblask ScrollToTop 2.0 true {b4fbcfd0-e862-44e6-8995-82e0a300fdd5} Smart HTTPS 0.2.1 true {b3e677f4-1150-4387-8629-da738260a48e} uBlock Origin 1.13.9rc4 true uBlock0@raymondhill.net uMatrix 1.0.1b6 true uMatrix@raymondhill.net Undo Closed Tabs Button 0.1.2 true {5997e7bd-1940-4058-a5f4-1562afce6353} Violentmonkey 2.6.3 true {aecec67f-0d10-4fa7-b7c7-609a2db280cf} All of them work flawlessly.
The developer of the extension "All-in-One Sidebar" AiOS has stopped developing it. But i guess this was expected - "The WebExtensions APIs that are available right now are extremely limiting when it comes to manipulating the browser's interface"
The Cyberfox developer can simply open his own webstore and instead of having to rewrite code - an expensive undertaking - keep legacy extensions alive. Would be worth it. That's what WF already plans to do.
re Open Tabs Next to Current - did you look at Always Right also? And do you know if there is / can be / will be an add-on bar replacement like Puzzle Bars / Add-On Bar (Restored)?
I had seen it but haven't tried it yet. It seems to be equivalent to Open Tabs Next to Current. Sorry, I've never user them. Perhaps you can open https://addons.mozilla.org/en-US/firefox/search/?sort=created&atype=&cat=&tag=firefox57&page= which only displays add-ons which are compatible with FF57. You might find a replacement in one of the categories at the left side. Re. Addon Bar (Restored): The latest commit on its github site was in 2014 - so it seems that it is no longer maintained.
Thanks. Yes, re Puzzle Bars, Quicksaver, who developed some excellent add-ons, has also thrown in the towel.
users webextension list: https://addons.mozilla.org/de/firefox/collections/yfdyh000/webextensions-for-tabs/ https://addons.mozilla.org/de/firefox/collections/grisfer/firefox/ (not all of them)
Firefox 54: Speed, customization and future Le future be bright? Or le future be bleak? So I've written an article discussing changes and improvements in Firefox 54, including multiprocessing, compact themes, other features and options, performance and responsiveness comparison to Chrome, interface customization, settings, addons, future implications, additional considerations, and more. Take a look. https://www.dedoimedo.com/computers/firefox-54-speed-customization-future.html Cheers, Mrk
You do realize on the ESR channel, you can stay with the old stuff until summer 2018? Who knows, someone may even open a webstore for them by then. All is not lost yet for old fogies like us. Progress isn't necessarily inevitable.
Of course I do, and I have that on a few computers. This was more to see what this brave new world offers. Mrk
beginning of 2nd passage of your conclusion is well spoken - thats it all rant about. comparison - not really possible - for now. i am using chromium now for several month, its another click and feel like firefox but under the hood its still a browser. what i noticed ist that a (naked) firefox has advantages in bookmarks speed and memory. the handling between firefox 57 and current chromium makes me struggle a bit - while chromium is more like current firefox i have problems with the new v57 menu and the rest of it. mozilla do not only make cuts in technology they also make it in usage. my purpose using - better: testing - opera/vivaldi/chromium was to learn, how firefox 57 would be. and for now i would say that i am not able to return to firefox, not complete, in parts. currently i am not able to rebuild in parts like it is now - not even close. and v57 is not ready yet, there is lot of work todo, each nightly has new issues, new major changes. maybe i try the early betas and will skip v56. maybe firefox 59 or 60 make me more smile (3 month later)
Well, everyone is entitled to his own opinion. However, what's annoying in your article is that you're comparing a several years old stable browser architecture (Google Chrome) with FF54 which is still actually an interim version within a large transition phase towards a new architecture. You write about FF54 lagging behind Chrome performance-wise and add-ons which won't work anymore. But you did not tell your readers that most Servo components from the Quantum project are not yet implemented/activated in FF54 (but will be in FF57). And you did not mention that a large number of APIs which already got Mozilla's okay are not yet available in FF54 (but will be - at least in great part - in FF57, and more will be certainly added). Your article suggests to an uneducated reader that FF54 is Mozilla's big hit but fail to mention that FF57 is intended to be it as that version will be the (preliminary) end of above transition phase. With these omissions you did your best to shy users away from Firefox. So your article is, IMO, unfair as it was written a couple of months too early. I'm disappointed. I expected better from you.
I compared what I can compare right now - a market product versus market product. What will happen in the future, who knows. As for the technical details, they are not important, because at the end of the day, you browse websites you don't relish in technical specifications of products. It's a simple usage case and what you get from doing what you do every day. If you think I'm being unfair - why did Mozilla then release an UNFINISHED product onto its users? If this is an interim version then it should not be the MAIN version that people use. And that's exactly the point - seamless transition. There isn't one. They could have build FF-SECOND, tested until everything was ready and dandy and then release. Instead, this is just developers having fun without consequences - or rather, nothing Mozilla did in the past six years helped with the market share, so how long is the interim going to last? Lastly, Firefox was great before the whole would-be Web 2.0 noise. The moment they started going "modern" they started losing themselves in this battle, and it continues to this day, with almost no benefits versus disruption the changes bring. A promise of something okay versus total destruction of 15 years of work. That's not a good deal. Mrk
It's not an unfinished product - it's a stable version. It's an interim version in the sense that not all new components are available yet. And why is a bad thing to integrate specific components which are ready to go so users can benefit of them? My main point was that you created the false impression for uninformed readers that with FF54 the big overhaul had come to an end and that it's still not competitive with Chrome.
Firefox with e10s enabled show tabs running in individual processes with a "low" integrity level. Chrome child processes currently run "untrusted". According to this article at Ghacks.net Mozilla will eventually introduce greater restrictions on Firefox processes, so to answer your question I believe there will eventually be parity between the two browsers. https://www.ghacks.net/2017/01/23/how-to-change-firefoxs-sandbox-security-level/
This is the wiki site which explains the details. I can confirm that Level 3 is enabled in FF57 Nightly. I'm not familiar with the sandbox used on Windows. For Linux namespaces and seccomp-bpf are used. I don't know if the details or specific rulesets are comparable with the Chrome sandbox but basically it uses the same technologies. As @Victek said, it's work in progress. Besides, it's also sandboxed with Firejail on my system, hence I'm not overly concerned
Regarding the move to webextensions you didn't mention that the motivation is not just cross browser interoperability, but the need to prevent extensions from "accidentally introducing vulnerabilities that could allow malicious code to execute with the full privileges of the browser". https://blog.mozilla.org/addons/2016/03/14/webextensons-whats-in-it-for-developers/
Yes, not only Mrk but many users who mourn XUL add-ons are missing this important aspect. That's why browsers like Waterfox which will still support legacy add-ons will undermine the new security architecture.
