You can’t do anything utterly complex or radical anymore. This so-called “customization” which is left in Firefox 57 is a joke. I think that’s a great shame and it will ultimately lose them a substantial part of their user base I’m sure.
Mozilla now is rapidly adopting Microsoft’s stragegy of bullying their loyal customer base into doing what they want rather than what users would prefer. Since CTR offered a workaround to circumvent Mozilla’s wishes, they’ve decided to mark it as WontFix. In that respect why does every browser have to look like Google Chrome? Unless Google has stipulated that in order to receive continued financial support for Firefox tabs must be placed above the location bar there’s no unearthly reason why Mozilla should place them above it and prevent users from reverting to the previous style. However, that’s obviously not the case given your contradiction.īut I still think it’s a shame that Mozilla is being choosy about which extensions they propose to support and CTR is one of the important ones for me because it allows me to place tabs below the location bar. OK, understood: I took Appster’s comment that you were a Mozilla Representative to mean that you were employed by them. Now You: What's your take on the revelation? Good news is that SeaMonkey won't go away, so that users who use it currently will be able to continue using it provided that they don't mind the changes that will be introduced based on the changes that Mozilla makes. SeaMonkey is a niche product, and the team that is behind the browser suite is well aware of that. The SeaMonkey Council is looking for support, not only financially, but also for contributors who help develop or maintain the web browser. This may be a definitive no at this point in time, but the team acknowledges that this may change in the future.īased on how successful Mozilla is, or if one of the forks gain ground, this might change in the future. SeaMonkey decided against switching over to one of the Gecko - Firefox's rendering engine - forks because they "do not have enough developers themselves to cope with the changes Mozilla plans", and because it is unclear whether they manage to keep up with the evolving web tech landscape. The current developer base is much too small to do our own fork. It is unclear how long we will be able to support classic extensions.Īlso, we are not planning to support any abandoned stuff like classic extensions and NPAPI plugins on our own. The most critical issue is to support web extensions in one of the next releases.
The team makes it clear that it does not plan to support features that Mozilla plans to drop, or has dropped already. This means that SeaMonkey will continue to support features such as the classic add-on system for a while longer before it is dropped (when the next ESR release hits).
SEAMONKEY PLUGIN CODE
This means, for the next couple of releases, that the team can continue to work on the current code base as security patches and bug fixes will mostly land in that time. It does not store any personal data.The SeaMonkey council plans to switch to Firefox ESR after the release of SeaMonkey 2.48. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin.
The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.
0 kommentar(er)
