On Mon, Sep 12, 2011 at 3:09 PM, snayrb99 <[email protected]> wrote:
> > Would it make sense to modify the plugin build to work with any future > of firefox (something like <em:maxVersion>*</em:maxVersion>?) rather > than tie to a specific version of firefox? I understand the reason for > being strict about versions in the past but with FF on a fast release > cycle it seems unlikely that plugin contract will change as newer > versions of firefox are released. This will not work. Under the new rapid release regime we must link against the gecko libraries with the proper module::kVersion set or the plugin will fail to load at runtime. > At a minimum, older versions of the > contract should be supported for a few releases giving FF plugin > developers a chance to migrate to newer versions of the contract on a > different release cycle. > Indeed, hopefully we get some deprecation period before the API actually changes, but this is up to Mozilla. Recently they were going to remove nsIDomWindowInternal (an API that we and many other plugins use) and have since backtracked and announced just a deprecation for FF8. Other APIs that we rely on may not be so lucky. > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
