Among them, FF. I authorized them and BAM! Congratulations for the genial idea you had. Really, congratulations. You erased the one advantage you had over all other browser, the possibility to do everything you wanted with the browser, and forever.
You threw away years of programming and user experience from thousands of people just like that. I, for one, will start testing other browsers immediately. Pale Moon is a good one to start on.
This means thousands of add-on was never supported by Pale Moon. Pale Moon is no alternative and Pale Moon is a browser with a totally outdated code base…. Anyone know a good web browser comparison site? I looked down to see that my menubar is missing. Firefox has broken it. How does that make users feel? Really, why break the extension now instead of sticking to your words and breaking them in November?
What a bad joke this is. Wait, here is a useful addon really? Currently, I can make it work on Firefox 57 nightly channel, using the following prefs: extensions.
I think so, but like I said, legacy add-ons will probably be significantly broken by then. I for one completely understand you guys moving away from the old addon model and most of the addons will be ported. On my current firefox install the only important addon that will not be ported is Classic Theme Restorer. I only really care about 2 of its features namely tab on bottom and hiding the Hamburger menu. I just hope that firefox does not break my prefered layout in the future.
Firefox 44 will remove the preference entirely. The roadmap mozilla. The realdownloader add-on was apparently disabled in Firefox on Can you please re-sign the add-on so I can use it without having to switch browsers? It worked excellent — until beginning of december. Is here maybe version 43 the culprit with its addon signing? The shared profile dir is still used from FF in both systems, so i have access to all bookmarks and addons.
But when i change the OS from Linux to Windows or vice versa the addons are always disabled with the first FF start, so i have to activate them manually. Otherwise if i start FF repeatedly within the same OS the addons be performed without problems. I have to say, every blog post I read erodes more good will that I have towards Mozilla and towards continuing with my add-ons. Not all of us want the latest build all the time. I hate to sound ungrateful, nor petulant, as I do prefer Firefox as a browser, but recently it seems as if updates, changes, etc.
Seems like the best solution for the poster is to use ESR. I am a bit confused, I am subscribed to Montreal Blog, but all of a sudden their content cannot be viewed as a pop-up comes forth stating they are being blocked by an Ad-block from my site? I have Aurora, and of my 14 add-ons, only 1, F1 my Mozilla Labs, is enabled? Have problems really been found with that many add-ons?
Tired of not having my add-ons, but would be willing to test if they were there. As far as I know, the version bump happened later in the process the first time than it will going forward. Maybe this upgrading of compatibility info should only consider the current versions of add-ons? I received three mails, for three outdated versions of my add-ons. All the current versions are already marked as compatible with 6. We only intended to bump the latest reviewed version plus any beta or unreviewed versions created since the last reviewed version.
I have a add-on with binary XPCOM component compiled to 6 or 7 platforms and unhappily, it seems not work anymore with Firefox 5?
So, I read the doc and see this,. See Binary Interfaces for details. Really you are joking? This means for me, impossible to maintain the extension. I have a wife, children, a job and other things to do that to compile betas of firefox each 3 months on 6 platforms…. Using these interfaces, and using dynamic calls to QueryInterface, it has been possible to write binary XPCOM components which were compatible with multiple versions of Firefox.
Beginning with Mozilla 2 Firefox 4 , this will no longer be supported: all status markings have been removed, and extensions that use binary components will need to recompile for each major version they wish to support. JS-ctypes is the recommended way for extensions to call into OS or third-party native code. If necessary, it is possible for an extension to support multiple versions by shipping multiple shared libraries DLLs in the same extension package, and selecting the correct version using versioning flags in its chrome.
Any way to opt out of these automated version bumps? Firefox 6? Otherwise, I suspect this is going to get annoying. Just a thought. This is weird since the extension is marked to be ok with: Firefox 3. The add-ons version was updated correctly to reflect the compatibility. Remote XUL has been a big maintenance problem, and has been the source for numerous bugs and security problems.
For this, remote XUL will be removed in Firefox 4. Luckily, HTML 5 already includes a fairly robust box model, so the main loss here is that web developers will not be able to use XBL on webpages anymore. Not all is lost, however. You should be able to easily manage the whitelist with this add-on. There are, however, many things included in this post that are not included in the article. You can also join our extdev IRC channel for one-on-one live help.
I usually hang out on that channel, but there are also lots of other experienced developers willing to help. Just join the channel and ask your question. Finally, if you have a featured add-on, or you want your add-on to qualify to be featured on AMO, you should take into consideration that after Firefox 4 RC1 is released, add-ons must be compatible with the latest release in order to qualify. RC1 is scheduled for January , so make your plans accordingly. Do you have a reference for this, Justin?
All I have read about it points to a bug that already has a patch. You can of course still build platform-specific stylesheets and provide different rules depending on where your toolbar button is displayed. But SVG images are supported to be used almost everywhere incl. CSS list-style-image in Firefox 4, so you might consider using those. The scaled result usually looks far better than scaled raster images. Latter would crop the SVG image instead of scaling it.
Part of the challenge for toolbar icons is to be able to have one xpi which can be installed on both firefox 3.
Is there an easy way to do that? Is there a way to us the firefox version in the CSS selector? This is better handled at the manifest level, rather than the CSS level. So, I recommend, that if you need different rules for 3. In general I think FF4 is going the right way. Unfortunatly, all the changes need to be documented and the examples have to be implemented or getting an update. At least you should focus on examples to replace no longer working examples. The example from the tutorials is no longer working in FF4 and it is unclear how to get custom toolbarbutton to the toolbarpalette.
Especially when there is no status bar visible by default, and under Windows the menubar not visible as well. Hope this is getting fixed soon, otherwise I already see a lot of fixed toolbarbutton getting on top. I love all the new tool bars we can add on but my back and forward button disappeared. I miss my back button alot, please return it. LOL I also wish there was some way it would be possible to stop hackers from invading our computers while playing games on face book.
I know some of you computer geniuses could figure something out. I use the Fission extension for the status bar problems. Fission puts the outgoing links into the address bar when hovered, along with the loading status up there, too. Firefox 4 will need something similar, already built in, to see all of that information. Thanks for breaking the thread manager without notice, without replacement and without documentation, all this between two betas.
You just leave developers with no alternative. With every release, development of Chrome extensions tastes better. I love Firefox, but Chrome extensions are SO much easier to code. Anyone know would the broken toolbarpalette in beta 7 be fixed soon? My addon cannot live without concurrency and Workers cannot be used, since I pass complex JS objects with methods etc between threads.
Creating icons is expensive, it involves art departments. Please fix this. There must be one icon for all situations and places and platforms.
0コメント