You're bringing back XUL? No? You must be removing the DRM on them instead? Also no? Then what are you doing? Copying google again/still.
What’s going on in the world of extensions
61–70 of 81 posts
Re: What’s going on in the world of extensions
#62Some more detail about the control that the new extensions button gives users: https://blog.mozilla.org/addons/2022/11/17/unified-extension... It allows you to disable extensions only on specific sites. (And presumably, that's also the reason you need to dive into about:config to remove it: if you remove it, it's pretty hard for casual users to find out why an extension isn't working. By gating it behind about:config…
I was checking this new extension button, I think is useful to give more light to extensions, but what I don't like it at all is that it only shows the extensions that are not present on the nav bar, not all your installed extensions. I think is confusing, it should be the list of all your extensions, and the user can pick which extension also appears more handy on the nav bar.
Re: What’s going on in the world of extensions
#63Earlier quoted context omitted.
I have taken the time to comment on the pull request before it was merged. I have mentioned several use cases, and offered an explanation for why the feature is important. If that is not enough for you and for Mozilla engineers, then perhaps the correct response is to simply abandon their platform. I've done my part, and I'm not going to further sacrifice my free time because some people have no concern about how the…
I will admit, I did miss your first message. But it was already responded to, with links to the bugs tracking the things that would have provided the functionality you requested. > All of this could have been averted by simply offering an alternative API in the same browser version in which the new restriction was implemented. You mean like manifests v2, which wasn't affected? I will also note, it was this comment in…
It will affect cross-platform extensions that need to migrate to Manifest V3 this year. Some projects will be forced to stay on Manifest V2 just for Firefox, substantially increasing development cost because of the need to maintain both MV2 and MV3 versions across platforms, or abandon a substantial part of Firefox users and only support the most recent browser version, assuming that a fix is even implemented in the browser.
Regarding your edit, I have not demanded anything, but asked if it would be possible to delay the release, for all the discussed reasons. For which I have received a non-answer, "it has already been merged" is not a valid reason for not correcting a mistake, and asking people to invest even more of their time in this and repeat what has already been discussed in a new bug report was just the last drop that made the lack of respect for other people's time obvious.
Re: What’s going on in the world of extensions
#64Earlier quoted context omitted.
I will admit, I did miss your first message. But it was already responded to, with links to the bugs tracking the things that would have provided the functionality you requested. > All of this could have been averted by simply offering an alternative API in the same browser version in which the new restriction was implemented. You mean like manifests v2, which wasn't affected? I will also note, it was this comment in…
It will affect cross-platform extensions that need to migrate to Manifest V3 this year. Some projects will be forced to stay on Manifest V2 just for Firefox, substantially increasing development cost because of the need to maintain both MV2 and MV3 versions across platforms, or abandon a substantial part of Firefox users and only support the most recent browser version, assuming that a fix is even implemented in the…
Is it Mozilla's fault Google marches on with MV3 with no regard to standards?
Mozilla will continue to support V2 and working towards V3 support. Expecting a fully compatible implementation on the first go is a lot. Especially since Mozilla has a fraction of the budget and other priorities besides aping Chrome.
Re: What’s going on in the world of extensions
#65Meanwhile in Firefox for Android: absolutely nothing is going on with extensions, because Mozilla disabled nearly all of them.
You can use Firefox nightly and enable any that you want. I'd rather use the version of Firefox that doesn't crash more frequently, but that's the trade-off I gotta make at the moment.
Okay, but that's not am acceptable trade off. There is zero reason why letting the user use arbitrary extensions and the unstable version should be connected.
Re: What’s going on in the world of extensions
#66Earlier quoted context omitted.
It will affect cross-platform extensions that need to migrate to Manifest V3 this year. Some projects will be forced to stay on Manifest V2 just for Firefox, substantially increasing development cost because of the need to maintain both MV2 and MV3 versions across platforms, or abandon a substantial part of Firefox users and only support the most recent browser version, assuming that a fix is even implemented in the…
Is it Mozilla's fault Google marches on with MV3 with no regard to standards? Mozilla will continue to support V2 and working towards V3 support. Expecting a fully compatible implementation on the first go is a lot. Especially since Mozilla has a fraction of the budget and other priorities besides aping Chrome.
The issue is not compatibility with Chrome. Projects that were otherwise ready for the Manifest V3 migration and have worked towards that goal in the last few months can no longer proceed with the migration, their work has been made obsolete. The code we wrote no longer works, and we don't even know how or if the issue will be addressed before the next major Firefox ESR release. If a solution is not released in the next few months, this issue will prevent some projects from migrating until the end of 2024, or they will have to contend with dropping support for Firefox ESR.
I hope reading the linked pull request thread and the comments here will make it easier to see what went wrong, and why listening to the people that work with these extension APIs is important.
Re: What’s going on in the world of extensions
#67It's upsetting to see all this corporate double-speak when Firefox fails to support the most basic extension functionally: the User Agent should allow the User to run their own code on their own machine without any requirement of phoning home to the manufacturer. This is currently impossible on Firefox as they forget extension loaded from local files to be removed after. The force everyone who wants to run their own…
You can keep your extensions loaded by setting this about:config value to false: xpinstall.signatures.required At least I think thats the one. Also extension updating can be disabled globally or on a per extension basis in the addons setting page. Edit: note that you have to package (zip) the extension. You can't keep an unpacked extension loaded.
Yes, but note that this only works in Nightly, Dev, Unbranded and ESR builds, not Beta or Release builds.
Re: What’s going on in the world of extensions
#68Some more detail about the control that the new extensions button gives users: https://blog.mozilla.org/addons/2022/11/17/unified-extension... It allows you to disable extensions only on specific sites. (And presumably, that's also the reason you need to dive into about:config to remove it: if you remove it, it's pretty hard for casual users to find out why an extension isn't working. By gating it behind about:config…
I was checking this new extension button, I think is useful to give more light to extensions, but what I don't like it at all is that it only shows the extensions that are not present on the nav bar, not all your installed extensions. I think is confusing, it should be the list of all your extensions, and the user can pick which extension also appears more handy on the nav bar.
That was in the original spec, but had to be changed because of technical constraints in the toolbar code.
Hopefully that can be addressed at some point in the near future :)
Re: What’s going on in the world of extensions
#69Meanwhile in Firefox for Android: absolutely nothing is going on with extensions, because Mozilla disabled nearly all of them.
Work on Android extensions got picked up again :)
https://blog.mozilla.org/addons/2022/12/15/new-extensions-av...
Re: What’s going on in the world of extensions
#70Meanwhile in Firefox for Android: absolutely nothing is going on with extensions, because Mozilla disabled nearly all of them.
Work on Android extensions got picked up again :) https://blog.mozilla.org/addons/2022/12/15/new-extensions-av...
We'll, that's something. 5 new extensions will bring the total up to 23. I still don't get why they make it so difficult to use any of the thousands of other extensions that are available.