![]() ![]() Properly made '''''plugins''''' shouldn't have been affected by Firefox updates. Read this answer in context □ 2 All Replies (5) We are also no longer able to support TwonkyBeam for any other browsers" While it will not expire, we are no longer going to provide updates. "Please note that TwonkyBeam 1.9 for Internet Explorer will be our last release of this product. So it looks like them blaming it on Mozilla is kind of disingenuous. Extensions will be assumed to be compatible and won't automatically be disabled just because of the update.Īccording to this page - Twonky is dropping TwonkyBeam support for Windows PC's with any browser. That is going to be different as of Firefox 10, which is slated for release on Jan 31. IOW, most extension developers using AMO didn't have that problem. ![]() However, most extensions on the other hand have needed "tweaking" for each new version that was released last year although extensions that were hosted at the official Mozilla Add-ons website have had the benefit of being automatically updated for each new version as long as the extension passed the "coding scan" for compatibility. Properly made plugins shouldn't have been affected by Firefox updates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |