-
Notifications
You must be signed in to change notification settings - Fork 15
Chrome seems to be broken #13
Comments
yes, sorry about that. The bug is confirmed since a while but I had no time to look into it and won't have for a while. |
Alright. Going to look into it. |
@damko Do you have a short instruction on how to get this running locally in chrome? Just adding the
Update: Nevermind. It still works. Seems to be a warning. |
you need to go in developer mode https://developer.chrome.com/extensions/getstarted |
Debugged for some time. Copied the exact same request chrome sends and put that into a REST api client (Insomia). I don't get a 302 there. Also used It works with Chromium and Chrome Canary (70). People from the Passman webextension have similar issues: Will try some other things when I find more time. |
In fact, if it works in FF it should also work in Chrome. It's a weird behavior. Anyway, thanks for the effort |
@damko I've had the same issue in floccus, here's the fix: nextcloud/passman-webextension#270 |
Thanks @marcelklehr. Created a PR based on this. |
thanks guys, very appreciated. I'm awfully swamped therefore I didn't yet have the chance to look into it. I'll do asap |
I have the extension installed in Firefox and Chrome with the same configurations. It does work in Firefox but doesn't in Chrome. The developer console shows constant redirects (302) to the target Nextcloud instance.
The text was updated successfully, but these errors were encountered: