This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Firefox 6/7 BETA Support
Comments
-
Hello Mark!
Be still, my beating heart. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />
Thanks for the update. It's déjà vu all over again!
Cheers!
BrandtFlag 0 -
Yep. Mozilla is on an accelerated development schedule now. It matches much more closely with the pace that Google set with Chrome. 1Password only officially supports the latest stable versions of the supported browser, and so far we have always been ahead of schedule in this regard. Support for the beta is very likely, given our track record, but we can't promise anything other than support for the final release. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />
Thanks for posting about this!Flag 0 -
Hi,
I'm currently testing Firefox 7 Aurora build, but 1Password plugin is not compatible with it.
AFAIK the addon API wasn't changed there, and this new version scheme by Mozilla is breaking many addons that in theory can still work.
I think if you will make the BETA plugin (that's why it's BETA, right?) work in the Aurora/Beta/Nightly versions of Firefox, many bugs can be found
before the actual release, not mentioning the fact that users like me will thank you.
Regards.Flag 0 -
Hello gurubez and joelw135!
I merged your topics with the appropriate thread.
Please review Khad's response, and let us know if you have additional questions.
Cheers!
BrandtFlag 0 -
[quote name='wmsec' timestamp='1310212689' post='31581']
Hi,
I'm currently testing Firefox 7 Aurora build, but 1Password plugin is not compatible with it.
AFAIK the addon API wasn't changed there, and this new version scheme by Mozilla is breaking many addons that in theory can still work.
I think if you will make the BETA plugin (that's why it's BETA, right?) work in the Aurora/Beta/Nightly versions of Firefox, many bugs can be found
before the actual release, not mentioning the fact that users like me will thank you.
Regards.
[/quote]
Hello wmsec and welcome to the Forums!
I merged your topic with the appropriate thread.
Please review Khad's earlier response regarding [url="http://forum.agile.ws/index.php?/topic/5492-firefox-67-beta-support/page__view__findpost__p__31540"]1P's support for Beta browsers[/url].
Let us know if you have any additional questions.
Cheers!
BrandtFlag 0 -
Hello neilio,
Please review my last post for the latest.
Cheers!
BrandtFlag 0 -
I know you don't want to develop against a moving target, and Firefox 7 is barely in alpha. But it's significantly faster than Firefox 5 during extended browsing sessions, and I'd love to be able to use it. Right now, the 1Password extension doesn't work; clicking the 1P button in the toolbar does nothing. Do you know if the add-on API has changed significantly, or if there's a simple fix you could implement to get the basics working?
If not, is there some way to take advantage of the bookmarklet in Firefox? I can't even figure out how to install it; the page that would let me drag-and-drop it into the toolbar seems designed for Mobile Safari.Flag 0 -
Firefox 6 is now in beta and is due for release in the middle of August. When will 1Password be updated to support Firefox 6?
Also, I work for Mozilla but not on anything that directly relates to how 1Password works. I have, however, followed some of the discussion of binary add-ons. I'm assuming that 1Password has a binary component. The recommendation that I've been seeing from people-in-the-know is that your best bet is to use JSCTypes to avoid having to recompile your add-on for each Firefox release.
In fact, as I understand it, a switch to JSCTypes might even allow people like me to run (and test) 1Password against pre-release Firefox much earlier in the cycle and give you feedback if there are issues.Flag 0 -
Hey Kevin!
Welcome back to the Firefox Q&A!
Your input was very valuable during the FF 5 lead up, and I'm glad to see you're back for the FF 6, and soon the FF 7, discussion.
As with FF 5, we do not have anything official to report regarding timing on support for browser versions currently in the beta stages. Khad states it best here: [url="http://forum.agile.ws/index.php?/topic/5492-firefox-67-beta-support/page__view__findpost__p__31540"]Mozilla Beta Support[/url]
However, as you are aware, we try very hard to meet customer demand, and I'm hoping the new accelerated schedules will not change that. Only time will tell.
I'm excited to hear more about the change to JSCTypes and how earlier testing may be possible. Please let us know more.
Cheers!
BrandtFlag 0 -
Hey there, Jay!
In all honesty, we haven't even looked at Firefox 7 seriously at this point. We are hard at work on supporting Firefox 6, and hopefully we will have something for that soon. Once that is done, I think our focus will be able to shift in that direction. Hopefully, the more aggressive release schedule will force Mozilla to stabilize their extension API and future versions will be a smoother transition for everyone. At least that is my hope.[img]http://forum.agile.ws/public/style_emoticons/default/biggrin.gif[/img]
Unfortunately, a bookmarklet is not really an option, as it was not designed with cross-browser compatibility in mind. It was a viable option for Chrome for some time only because Chrome is also based on WebKit. I am sorry I don't have better news for you right now, but keep your eyes open! We will let you know as soon as we have something new for Firefox. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />
[quote name='Jay Levitt' timestamp='1310738329' post='32079']
I know you don't want to develop against a moving target, and Firefox 7 is barely in alpha. But it's significantly faster than Firefox 5 during extended browsing sessions, and I'd love to be able to use it. Right now, the 1Password extension doesn't work; clicking the 1P button in the toolbar does nothing. Do you know if the add-on API has changed significantly, or if there's a simple fix you could implement to get the basics working?
If not, is there some way to take advantage of the bookmarklet in Firefox? I can't even figure out how to install it; the page that would let me drag-and-drop it into the toolbar seems designed for Mobile Safari.
[/quote]Flag 0 -
[quote name='bswins' timestamp='1310766692' post='32100']
I'm excited to hear more about the change to JSCTypes and how earlier testing may be possible. Please let us know more.
[/quote]
JSctypes is outside the realm of my expertise, though I'm sure there are people in our add-ons support areas that know how to best make use of it:
https://wiki.mozilla.org/JSctypes
I'm assuming that the main problem with 1Password working on new Firefox releases is because of a binary component (though that may not be a correct assumption). If it is correct, then using JSctypes instead of building a binary XPCOM component can really simplify the support of new Firefox versions.
If your developers attempt to use JSctypes and have trouble, I can try to connect them with the right people to get help.Flag 0 -
[quote name='dangoor' timestamp='1311105061' post='32361']
JSctypes is outside the realm of my expertise, though I'm sure there are people in our add-ons support areas that know how to best make use of it:
[url="https://wiki.mozilla.org/JSctypes"]https://wiki.mozilla.org/JSctypes[/url]
I'm assuming that the main problem with 1Password working on new Firefox releases is because of a binary component (though that may not be a correct assumption). If it is correct, then using JSctypes instead of building a binary XPCOM component can really simplify the support of new Firefox versions.
If your developers attempt to use JSctypes and have trouble, I can try to connect them with the right people to get help.
[/quote]
Hi Kevin,
Thanks for the response. I checked out the Mozilla wiki page, and I'm convinced that it is outside my realm of expertise too! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />
As Khad stated, we all appreciate your willingness to help.
Thanks again!
Cheers!
BrandtFlag 0 -
[quote name='Chet' timestamp='1311284898' post='32779']
More; 1Password is not available in FireFox 6 either as a menu button or as a contextual menu option.
[/quote]
Hey there, Chet! I hope you don't mind, but I moved your post to the appropriate thread.
We don't currently support Firefox 6, but we are working on it and hopefully we will have support ready for it when it is released. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />Flag 0 -
are we there yet? are we there yet? are we there yet?
I know, you don't give out timeframes and they aren't of any help. Things are done when they are done - the sooner the better, but workpower is limited. I understand all that but since I didn't find any thread about Firefox 6 beta support, I thought I'd create this one to raise my voice that it is needed.
Hope to see that soon <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />Flag 0 -
I tried editing the install.rdf to maxversion of 99 but I see that's just for FF compatibility. The only difference between FF4 and FF5 extensions seem to be in the libosxform_xpcom.dylib file. Is there something in that file that limits it working with different versions of FF? I'm stuck having to use the lastpass extension with my 1Password exported database in order to use FF7/8 which is horrible in comparison to 1Password. FF5 is just too slow on my older laptop and doesn't include the memory leak fixes and 2D speedup which I need so desperately. I'm using the beta version of 1Password but it doesn't include any beta extension support. Is there a test build of the extension we can try out? Without needing any support from you of course.Flag 0
-
[quote name='pooprscooper' timestamp='1311744769' post='34299']
I tried editing the install.rdf to maxversion of 99 but I see that's just for FF compatibility. The only difference between FF4 and FF5 extensions seem to be in the libosxform_xpcom.dylib file. Is there something in that file that limits it working with different versions of FF? I'm stuck having to use the lastpass extension with my 1Password exported database in order to use FF7/8 which is horrible in comparison to 1Password. FF5 is just too slow on my older laptop and doesn't include the memory leak fixes and 2D speedup which I need so desperately. I'm using the beta version of 1Password but it doesn't include any beta extension support. Is there a test build of the extension we can try out? Without needing any support from you of course.
[/quote]
As I understand it (and I am not an expert on this), binary extensions to Firefox (like the libosxform_xpcom.dylib) require recompiling with each significant Firefox release. This is undoubtedly going to be a bit more challenging for 1Password, given a new Firefox release every 6 weeks, though it may just require a recompile and nothing more than that. Firefox has another mechanism, JSctypes, which can apparently alleviate this pain.
In short: upping maxversion in install.rdf isn't enough.Flag 0 -
[quote name='dangoor' timestamp='1311773286' post='34354']
As I understand it (and I am not an expert on this), binary extensions to Firefox (like the libosxform_xpcom.dylib) require recompiling with each significant Firefox release. This is undoubtedly going to be a bit more challenging for 1Password, given a new Firefox release every 6 weeks, though it may just require a recompile and nothing more than that. Firefox has another mechanism, JSctypes, which can apparently alleviate this pain.
In short: upping maxversion in install.rdf isn't enough.
[/quote]
Hopefully they can switch over to JSctypes then as it should make it easier to deal with Firefox's 6 week release schedule as well.Flag 0 -
[quote]As I understand it (and I am not an expert on this), binary extensions to Firefox (like the libosxform_xpcom.dylib) require recompiling with each significant Firefox release.[/quote]
Yup. That is why we are actually planning to just use a pure JavaScript extension. That makes it easier to use the same codebase in all browsers [i]and[/i] keep up with the quickened release schedules (for Chrome and now Firefox as well).Flag 0
This discussion has been closed.