Autofill working intermittently (mostly not) with Chrome extension for Twitter.
I have a lot of client twitter accounts, so I log in and out all the time. Recently Chrome's 1password extension simply will not fill for twitter, forcing me to copy and paste.
It's just Twitter. I don't have trouble with it elsewhere.
A quick test with Firefox (I also have that extension) shows no trouble, though there is an interesting delay before it populates the fields.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Comments
-
@gordonatkinson61: Thanks for reaching out. That's really strange! I just did a sanity check here, and it seems to be working for me. So there's probably some difference there in your case. Unfortunately without some basic information it's hard to say what might be going wrong and how we might right it! Please tell me the OS, 1Password, Chrome, and extension versions you're using, the exact steps you're taking, and what is (or is not) happening the way you expect so we can figure out the best plan of action:
Find your version
The more information you can give, the better. For instance, knowing the URL will let us rule out an issue with the particular login page. Thanks in advance! :)
0 -
0 -
Clicking the chrome extension sometimes fills in the login fields. usually will not.
0 -
Thanks for the screenshot showing the exact URL for Twitter you're using, however we still need to know the rest of the information Brenty asked for:
Unfortunately without some basic information it's hard to say what might be going wrong and how we might right it! Please tell me the OS, 1Password, Chrome, and extension versions you're using, the exact steps you're taking, and what is (or is not) happening the way you expect so we can figure out the best plan of action:
Find your version
The more information you can give, the better.
Please let us know about all that when you get a chance, and we'll continue from there. :)
0 -
@gordonatkinson61: Ah yep, I was just filling on the main page too. I was wondering if you had an absurd amount of tabs open as I do, but it seems like that's not the case. Do you perhaps have other extensions which might be interfering? Hopefully we'll be able to narrow this down with some additional information. :)
0 -
Sorry. Must have been skimming.
-Mac OS X 10.11.6
-1Password 6.7.1 (671001)
-Chrome Version 58.0.3029.96 (64-bit)
-1Password: Password Manager and Secure Wallet 4.6.5.90When I go to Twitter I click the 1Password extension. Nothing pops into the login box. If I repeat, sometimes the second time works. It's always been a little glitchy but when it failed it always worked on the second try, so I never cared.
In the last week or so, suddenly it just refuses to populate. So I end up manually copying the login info out of the extension and pasting it.
Gordon
0 -
Okay. So I just went to test something. Wondering if it does this when I first open twitter or JUST when I would log out of one account. Suddenly it's working. It's not been working for me for a few days now. But right now it worked.
So I'd count it as intermittent and probably worth looking into on your end. But I felt obliged to mention this. I'll keep monitoring.
0 -
@gordonatkinson61: Thanks! I have a nearly identical setup, except I'm using Sierra.
When I go to Twitter I click the 1Password extension. Nothing pops into the login box. If I repeat, sometimes the second time works. It's always been a little glitchy but when it failed it always worked on the second try, so I never cared.
I hear ya. I'm wondering if it's simply that it's failing sometimes when the page hasn't fully finished loading. Do you have the same problem once it's done? How about if you use the keyboard shortcut to fill (
⌘ \) instead of the mouse? These may be rhetorical questions now if you're not having trouble, but if it happens again please let us know. :)0 -
Thanks. I'll try making sure the page is loaded and the shortcut if and when it happens again.
0 -
There is a weird and intermittent bug that we're working on that may be the cause here and as you're a Chrome user there is a way to check. If it happens again can you right click anywhere on the page and select the Inspect menu option in the contextual menu please. This will open a new Chrome Window whose title starts with the words Developer Tools. Along the top are some tabs and one is titled Console, can you click here and either take a screenshot or copy and paste if you see anything in red. If it's related I think you will see something. If you do the good news is we are working on eliminating this bug which should mean a new version fixes this.
ref: OPX-1361
0 -
WOW, you guys are on top of this. The response to this rather small issue is very impressive. @littlebobbytables, I'm a website developer and social media professional. I'm very familiar with the inspect tools in Chrome. I use them all the time to check css stuff. So I will definitely do that if it happens again.
I was toying with the idea of replying but, knowing it might open the ticket up and cause you to need to reply again, I wasn't going to. But it's like magic today. After probably 2 weeks of MOSTLY not working, the chrome extension is working like a charm on Twitter. But it has come and gone. So next time, if there is one, I'll do this and send you the screenshot if anything is red.
0 -
Never feel like you can't reach out to us. That's what we're here for! While I'm glad to hear that it's working for you now, I'm not sure we can take credit (yet) as we haven't released a new version to address that in particular. But while I'm afraid that it's likely the issue may return at some point, we're here for you. Thanks for the kind words, and likewise for your willingness to work with us on this. :)
0 -
@littlebobbytables Okay, this morning Twitter is again refusing to fill the sign in fields with the 1password app. Here is a screenshot and pasted text from the Console which indeed shows some red errors.
17.commons.en.79f67e9addb1f516d339.js:21 Refused to load the script 'https://cdn5.userzoom.com/files/js/QzI2OVQxNDMg.js?t=uz_til&cuid=2BA733EB49F6DF1188490022196C4538' because it violates the following Content Security Policy directive: "script-src https://connect.facebook.net https://cm.g.doubleclick.net https://ssl.google-analytics.com https://graph.facebook.com https://twitter.com 'unsafe-eval' https://*.twimg.com https://api.twitter.com https://analytics.twitter.com https://publish.twitter.com https://ton.twitter.com https://syndication.twitter.com https://www.google.com https://t.tellapart.com 'nonce-3J7eFTLhyIgaLPwxsiYghQ==' https://platform.twitter.com https://www.google-analytics.com 'self'".
2twitter.com/:1 Error in event handler for runtime.onMessage: TypeError: Cannot set property '__0' of undefined
at chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk/end.min.js:77:487
at T (chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk/end.min.js:77:210)
at Pa (chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk/end.min.js:37:53)
at Ma (chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk/end.min.js:34:120)
at chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk/end.min.js:43:224
0 -
Greetings @gordonatkinson61,
So not great that you're seeing this but good news that it is the same issue we've had reported and that we're working on. What I can't understand is why this is cropping up now as when I looked at the files it seems we haven't mucked about with this in ages. Regardless, we hope to have something soon that behaves better :smile:
0 -
Great. Thanks. I think this does it for this thread. I'll live with this and know that perhaps it will be solved in a future release. Appreciate the response on this!
0 -
:) :+1:
0 -
We have just released 4.6.6.BETA-1 and I'm hoping it's going to help :smile:
If you're interested, the following will allow you to test the new beta.
- Uninstall the existing 1Password Browser Extension installed in your browser.
- Restart your browser. This is to avoid weird caching nonsense.
- Download and install the beta from 1Password Browser Extensions.
The issue wasn't as simple as a bug but this weird intermittent behaviour where we'd set something and then it disappeared on us later. So we approached the entire task from a slightly different angle to bypass the weirdness. Given the frequency which you found this on Twitter I'd love to hear if you find the issue doesn't return when running the beta.
0 -
I'll install it, give it a try - particularly with Twitter - and report back.
0 -
:+1:
0
