@leocg said in Adblocker not existing on google and FB?:

Try removing the sites from the adblocker exception list.

who in hell added these? I wasnt it.

also why do all the other entries just show the adblocker icon but just without color for showing that the adblocker is disabled here with the option to re-enable them. these removed the adblocker from those sites ENTIRELY.

why does the adblocker not appear on google and Facebook anymore, how can I get it back?

@mgeffro Github and Google don't really surprise me. if I remember correctly, these weren't being asked on chrome meaning the registration just passed. although it might be worth a look for the recent chrome source since it changed the result of that dialog. Deny is now no longer an error but instead chrome changing the attestation cert and masking the U2F device.

it in general might be good to let all dialogs from chrome pass through somehow (if possible) even if they look awkward, unless opera properly replaced or otherwise dealth with them, better awkward than not working

@nvmjustagirl said in U2F registration issues:

Are you on a desktop computer.. laptop..
Note - Since this computer lacks a platform authenticator, the website may require the user to present their USB security key from time to time or each time the user interacts with the website. This is at the website’s discretion

desktop but irrelevant, it isnt the website kicking me out but the U2F not triggering (recent) or the registration triggering but failing hilariously (earlier issue), with the recent one being confirmed by opera meaning it isnt the website doing weird stuff.

@mgeffro said in U2F registration issues:

@my1xt I can confirm that recently we fixed issue with U2F not working on on our beta (55) and developer (56) streams. It was already fixed in latest developer release and should be available with next beta update. Will have to look into the registration issue.

Okay nice to know that at least login will work again.

Regarding U2F Register while I did state it a bit weirdly I still believe this is an issue which has been brought from chrome but opera not having been prepared for it!

0_1533713445433_Screenshot (492).png

@vashiru said in U2F registration issues:

@nvmjustagirl This doesn't solve the issue. The Web Authentication API is already enabled. I can use it to authenticate. It's just the registration of new U2F keys that's broken.

well funnily enough I now cant even auth anymore in Opera (Beta 55.0.2994.29) the U2F device wont even blink. Chrome and Vivaldi on the other hand just do both registering and Authing.

@l33t4opera why not make a setting for this? everytime I add stuff to the dial I need to move them cause the newly added ones kill the arrangement when they come on first.

@burnout426 It might also be a mouse hardware issue. my mouse for example has the issue that it sometimes fire a double click instead of a single one, which can happen when the contact of the button isnt perfect.

logging in isnt the problem.

Adding a key is the problem.

while some sites like the yubico demo page spawn on both chrome and opera a notification asking whether the site may get key data, some other sites like github, dropbox or localhost dont spawn such a notification and while they just pass in chrome, opera throws U2F error 1.

more info here:
https://forums.opera.com/topic/26772/u2f-registration-issues