I'll just keep updating this thread whenever I notice a new version ...
1Password Beta - Version: 126.96.36.199939 does not fix this.
My I ask, why you prefere using Chrome betas above Chromium betas? I can't seem to figure any good reason for that. The only difference is that Google does it's best to make some money mining all your data with chrome. That is not happening with Chromium and that's why I have a hard time trying to understand why some users prefere Chrome above Chromium.
Mainly because I want to be as close as possible to what most Chrome users are using.
I'm not against Chromium, it's just yet-another configuration I need to maintain. Indeed, I had Chromium on my last MacBook Pro but it didn't survive the recent upgrade
I'm pleased I was able to recreate the issue in Chromium and I'll investigate this further but I am very confused about the version numbering. Is Chromium really supposed to be 2 major versions behind Chrome's development version? I thought the entire point of Chromium was to be on the bleeding edge? Or, is the preference solely based on removal of the data mining aspect of Chrome?
Is Chromium really supposed to be 2 major versions behind Chrome's development version? I thought the entire point of Chromium was to be on the bleeding edge? Or, is the preference solely based on removal of the data mining aspect of Chrome?
That's what I was trying to say with my recent posts: afaik, chrome and chromium are identical except chromium being the open source version without all the google data-mining going on. They are the same when it comes to stable versions. This is what the FreeSMUG is providing: stable builds of chromium, which will have the same version numbering. Not sure though about betas and I'm almost sure that the nightlies will differ.
I hope I wasn't the one causing chromium nightmares for you! Sry that this followed you into the night, were you actually should rest.
Google Chrome 12.0.712.0 (Official Build 79102) dev
WebKit 534.27 ([email protected])
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/534.27 (KHTML, like Gecko) Chrome/12.0.712.0 Safari/534.27
Command Line /Applications/Chrome Dev.app/Contents/MacOS/Google Chrome -psn_0_1011959 --flag-switches-begin --flag-switches-end
I can confirm that the 1Password Beta Chrome Extension [font="Helvetica, sans-serif"]Version: 188.8.131.52943 works with the auto-unlock settings now in Chromium (12.0.734.0 (81353)). [/font][font="Helvetica, sans-serif"]
Since this fix is for Chromium only, it doesn’t fix the Chrome dev version for me
To clarify this:
So Mike isn't 100% correct when he states that chromium is nightly only. Look at the stable releases (linked above) and you'll see that version numbers are the same. That's why I'm so puzzled that end-users choose to rather use chrome instead of chromium. Is it so hip, to give all your data to a company only interested in profit? With google people have to realize they are not customers but they themselves are the product (often used thesis. e.g. here: http://itmanagement....the-Product.htm ).
AFAIK I am using the latest Chrome Development release (12.0.733.0 dev) and the unlocking is working fine. Where did you get yours from?
AFAIK, 12.0.712.0 dev is the latest Chrome Dev build for me. The build is from the official Dev channel at Google's Chromium page: https://sites.google...ved/dev-channel
I just downloaded it again from that site, it's still 12.0.712.0 for me.
Dave, I trashed it with the plist. That finally got my up to your version, I’m not sure why that worked.
After this, Chrome Dev, Beta and Stable now works with your new extension. WOOHOO!