Steam links no longer open (1.14.1077.41)
-
I just upgraded from the last 1.13 stable to 1.14.1077.41. Previously I could click on "Open in Steam" links on the Steam store & they'd open in the desktop client (for eg: steam://store/585180)
Now I'm getting an error:
This site can’t be reached
The webpage at steam://store/585180 might be temporarily down or it may have moved permanently to a new web address.
ERR_UNKNOWN_URL_SCHEMEAny idea for a fix? Every new major version makes the browser less functional for me.
-
@alexdante It is a bug introduced by Chrome. They will fix it in due course. Nothing for Vivaldi devs to waste their time on here.
-
@pesala If they're using a bugged version of chromium as the basis then they have a very different definition of "stable" from the rest of the industry.
-
@alexdante All software has bugs. As long as they are not critical then development must go forward, not backwards.
Magnet and Steam links are not needed by the majority of users.
-
@pesala Ah nice, "I don't need it so you don't need it". Good job.
BTW it works perfectly fine in Chrome 64.0.3282.119 (Official Build) (64-bit). So, uh, what was that excuse again?
-
@gwen-dragon then it should be fixed but it's not
-
@alexdante said in Steam links no longer open (1.14.1077.41):
Ah nice, "I don't need it so you don't need it". Good job.
That is not what I said, and you know it. Development should not be put on hold due to non critical bugs.
I reported this regression for the latest snapshots. It is still broken in Final. That's life. It affects me a lot, but maybe not others. It's certainly not critical, I just have to log-in very often.
(VB-36679) Logins Lost on Restarting Vivaldi
-
@gwen-dragon maybe something gets lost in translation here, let's reword:
Chrome 64.0.3282.119 works with those URI, Vivaldi has 64.0.3282.121 which is 2 subversions NEWER than Chrome (121 vs 119) and it's not working with those. Something wrong is in Vivaldi, for what I understand. -
@ian-coog said in Steam links no longer open (1.14.1077.41):
Chrome 64.0.3282.119 works with those URI, Vivaldi has 64.0.3282.121 which is 2 subversions NEWER than Chrome (121 vs 119) and it's not working with those. Something wrong is in Vivaldi, for what I understand.
Not quite what @Gwen-Dragon said, the "bug" was introduced in Chromium after 64.0.3282.119.
So it was introduced in either 64.0.3282.120 or 64.0.3282.121. -
@tbgbe the bug was there in chromium 64 for weeks before .119 which is the one that is declared fixed.
It's been weeks the bug get reported in the forum (I also made a proper bug report myself) way before .119 got released, which was some days before 1.14 rc1 -