We had no difficulty with any of the interfaces we used with Firefox 3.1 beta 1. I thought that it’s probably due to work in progress on the “places” component, but just in case, I thought it would be a good idea to list it here. I was trying to retrieve the site icon through the “nsIFaviconService”, “getFaviconImageForPage” method, and the code that worked for 3.0 will show always the default document icon for 3.1. I assume this means that various other functions have been shifted from browser.js also. With my extension I found that a function, canonizeURL, had moved from browser.js to urlbarBindings.xml and now returned a value. Your assistance will be invaluable in helping us identify migration issues and ensuring that Firefox 3.1 has high rate of add-on compatibility upon release.Ĭategories: compatibility, developers 43 responses You can provide feedback as a comment to this post and any information will help, even something as simple as: We are interested in any issues you’ve encountered including interface changes, unanticipated behaviour or any API updates. Some of you have already updated your extensions to Firefox 3.1 beta, or are in the process of doing so, and we’re asking for your help by providing some useful feedback about the migration. In order to help add-on authors migrate to Firefox 3.1, the Mozilla evangelism team is working on documenting changes between Firefox 3.0 and Firefox 3.1 which could affect extensions.
0 kommentar(er)
