This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Future Firefox Builds (Beta and Andromeda Channels)
<div class="IPBDescription">Why does 1Password keep breaking on every beta?</div>Hi,
I notice it took a while for you to update to support the Firefiox5 beta and just in time for the release.
However, the Andromeda (which will become the next beta FF6) it doesn't work.
My question is, do they change FF infrastructure so drastically on every beta/version that it is so complex for 1PW to work on the betas?
Or is it just some compatibility string you put in the code which you need to update.
It seems hard to believe (but I don't have extensive experience in such matters) that it changes so much that it takes weeks of 1Password coding to make it compatible with the latest builds.
Is there something you can do to make the 1PW betas more compatible and at least work (albeit in beta mode) for the future builds considering the accelerated pace of FF releases, and, our intense need to have, and not live without 1Password while wanting to live on the bleeding edge of these technologies and test them?
Thanks in advance for patiently explaining the situation <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />
dbw77
I notice it took a while for you to update to support the Firefiox5 beta and just in time for the release.
However, the Andromeda (which will become the next beta FF6) it doesn't work.
My question is, do they change FF infrastructure so drastically on every beta/version that it is so complex for 1PW to work on the betas?
Or is it just some compatibility string you put in the code which you need to update.
It seems hard to believe (but I don't have extensive experience in such matters) that it changes so much that it takes weeks of 1Password coding to make it compatible with the latest builds.
Is there something you can do to make the 1PW betas more compatible and at least work (albeit in beta mode) for the future builds considering the accelerated pace of FF releases, and, our intense need to have, and not live without 1Password while wanting to live on the bleeding edge of these technologies and test them?
Thanks in advance for patiently explaining the situation <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />
dbw77
Flag
0
Comments
-
[url="http://forum.agile.ws/index.php?/topic/4859-firefox-5-support/page__view__findpost__p__28552"] Déjà vu[/url]? <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_tongueout.png' class='bbc_emoticon' alt=':-P' />
[indent]Please keep in mind that … while we are always excited to support beta, alpha, and "bleeding edge crazy" browsers, much of that is a result of little to no changes in the browser which require a complete rewrite/recompile/etc. Chrome is a great example of this. The Chrome extension often breaks in channels other than stable (beta, dev, etc.) but we continue to focus our development efforts on the stable version (while looking ahead to see what will soon become the next stable version). Often, 1Password "just works" in Chrome's beta/dev/canary channels, but this is not usually a results of specific targeted development. Sometimes we all just get lucky. Beta/dev/alpha/crazy builds are not meant for daily use but for developers. 1Password works great in the latest stable version of all major browsers and [i]even supports some more[/i] (like Safari 5.1) in addition. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />
Mozilla has only recently shifted their development cycles for Firefox to a pace similar to Google's with Chrome. There are some changes we need to make in our own development cycle to better accommodate this, but Mozilla is likely going to be changing fewer things between releases with the new development cycle. So the upshot is that while we are in a transition period right now, future Firefox releases may very well be support much more quickly once everything is adjusted. The timing wasn't ideal with WWDC fast approaching and Lion support being such a high priority, but we are trying to squeeze it all in (while still spending time with our families who miss us sometimes).[/indent]
In addition to what I wrote in our earlier conversation, I would add that Firefox is requiring extensions to be recompiled for each version, and Firefox support is not the only thing developers have been spending their time on. We are preparing for Lion, Safari 5.1, and other goodies which I can't discuss at this time. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />
As I said before, I imagine the process will only become more streamlined in the future. This was a transitional time for Firefox, WWDC was going on, and we are planning to unify the codebase of all of our extensions which will help [i]everyone[/i] (not just Firefox users).
Please let me know if there is anything else I can help with.
Cheers,Flag 0 -
[quote name='khad' timestamp='1308792890' post='30065']
[url="http://forum.agile.ws/index.php?/topic/4859-firefox-5-support/page__view__findpost__p__28552"] Déjà vu[/url]? <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_tongueout.png' class='bbc_emoticon' alt=':-P' />
[/quote]
All over again! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/wink.gif' class='bbc_emoticon' alt=';)' />Flag 0