Vivaldi.net notifications etc. broken in current Chrome for Android
-
I'm surprised no one else has reported this... I can't seem to use the notifications icon or show the left hand selection by swiping right after updating Android to Chrome 65.0.3325.109.
Is it just me...?
Btw. It doesn't even work if I select desktop mode...
-
I can get it all to work on the device emulator in desktop Vivaldi, so it's odd that it wouldn't work in a mobile browser.
-
@lonm Well I came here again just now since I have a notification... But can't find it what it's for! Checked the threads I usually view, then came here - but it still shows 1 unread.
Other sites with similar functions don't have a problem...
I'll try to remember to update Chrome on my tablet to test if this is a weird error only on my phone.
-
I can confirm that this is an issue and not just something specific to my device.
I just tried using my work phone, which is also up to date with Chrome, and the exact same problem: when I click on the hanburger menu on the forum, the menu button goes dark but nothing else happens.
My work phone is only used for e-mail, with almost all options and software left at default - and I've never used it to look at the forums before (and I didn't log in) - so I'm quite sure that this is not a problem with my settings...
It seems like this should be affecting everyone using the latest Chrome on Android, so I'm surprised I'm the only one saying anything...
-
@gwen-dragon This seems to be an issue in the Vivaldi forum engine (or in Chrome for Android). I thought the bug report template was only for Vivaldi's issues?
-
@guilimote yeah, I know how to report a Vivaldi bug. I came here since I thought this is the place to post forum bugs!
Edit: [checks forum title] yep... "report a forum issue"
-
@gwen-dragon ah ok, thanks for the clarification
-
Seems like you have reached a solution by yourselves already
Still wanted to stick my nose in the discussion here cause I tried Chrome Beta, which is as of now on Chromium 66, on my Android phone, and it worked as expected. So time is cure I guess.I'm assuming that the issue is what is mentioned in the following pages:
-
Can confirm that since Chrome updated on my phone there is no longer an issue... So no bug filed
-
@mossman Cool Thanks for confirming!