lxyu 0 Posted December 25, 2011 Posted December 25, 2011 The evernote web clipper is incompatible with firefox aurora channel, I'm waiting for the fix since aurora 10.0, and till the aurora update to 11.0 recently, it's still incompatible.I have 10+ plugins installed, and the web clipper is only one incompatible even after I switched the firefox incompatible check off. So I think may be the fix won't be too difficult?Have you guys ever consider check and support aurora channel?
Owyn 457 Posted December 25, 2011 Posted December 25, 2011 Evernote officially supports only stable releases of the major browsers (Internet Explorer, Chrome, Firefox, and Safari).
ric 17 Posted January 6, 2012 Posted January 6, 2012 But hopefully you aren't waiting for the official releases before starting development of the next extension version, particularly since the clipper extension seems to break with every new version. It would be nice if you would release beta or alpha versions to go along with the beta/aurora channels, even if they are not officially supported.
Level 5* jefito 5,598 Posted January 6, 2012 Level 5* Posted January 6, 2012 But hopefully you aren't waiting for the official releases before starting development of the next extension version, particularly since the clipper extension seems to break with every new version.They probably track them internally, yes... It would be nice if you would release beta or alpha versions to go along with the beta/aurora channels, even if they are not officially supported. ..but I think they've decided that it's not worth it to time Evernote clipper betas on Googles *and* FireFox's schedules, at least publicly.
jbignert 473 Posted January 6, 2012 Posted January 6, 2012 Posted a FF10 beta version in a new thread. Please report any issues you have on that thread.http://discussion.evernote.com/topic/23085-firefox-10-web-clipper/
Level 5* jefito 5,598 Posted January 7, 2012 Level 5* Posted January 7, 2012 I stand corrected, but in the circumstances, that's OK. Thanks jbignert!
Owyn 457 Posted January 10, 2012 Posted January 10, 2012 Compatible by defaultThe first and most important thing to note is that starting in Firefox 10, add-ons are assumed to be compatible by default. Unless you use the <em:strictCompatibility> flag in your manifest, Firefox will no longer mark your add-on as incompatible after an upgrade to Firefox 10 or later. You can use that flag to ensure that an add-on that is likely to break will not try to run in updated copies of Firefox. It's worth noting that add-ons that have binary components will always be strictly checked for compatibility, since binary components always need to be recompiled for each major Firefox release.https://developer.mozilla.org/en/Firefox/Updating_add-ons_for_Firefox_10This should help a lot going down the road.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.