4.0.2312.24 crashes on ElCapitan 10.11.6
-
@bnmnesta FYI, the Vivaldi team is working on getting a fix out ASAP; hopefully VERY soon.
Perhaps it's time I move on. @xyzzy explanation that they don't have "many Snapshot testers running macOS 10.11.6" is funny. Why release for a platform if you cannot, or have not tested? When you consider the time this has taken, and consider the silence for a week, it's well past disappointing.
Your frustration is understandable. I also don't recall this sort of thing ever happening before... and I also used to have a Mac that I couldn't update past 10.11.6 as well. I also hope that the Vivaldi team can continue to support older Macs. However, there will come a day when either the Chromium team will raise their minimum system requirements or it will be impossible to develop software for the newest versions of macOS and still maintain compatibility with older systems.
-
FYI, the Vivaldi team has released an update that should fix this crash: https://vivaldi.com/blog/desktop/minor-update-3-for-vivaldi-desktop-browser-4-0/
-
@xyzzy yes, working now (4.0.2312.33). thanks
-
Now it works well
Vivaldi 4.0.2312.33 (Stable channel) (x86_64)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36Thanks Vivaldi!
-
@xyzzy Seeing how the computer world works today, I understand that in the end they stop giving support. But the logical thing would be to mention it on the front page: "from this version 4 the X, Y, Z systems do not work ... and the requirements are these".
And of course, the most important thing: mention those same requirements both on the main page and on the download page. In aid. Everywhere. And do not do as many: assume that everyone uses the latest version, whatever it is. Or limit the help to "update, update, update ...".
And never mention from which versions it works or that other feature. Or system. Before, at least it was said: "from version 2 you can use iCloud, from 3 iCloudDrive, and from 4 SuperICloud2000"
Now everyone assumes that you use the latest of the latest, and that tomorrow it will be obsolete. Even just for 24 hours. And they don't even accept that this is not the case. Nor do they care the least for those who don't. They do not exist. -
too much hate from some people to devs who do their job. guys, nobody owes you a thing, relax, be thankful for prompt fix and support of old OS, most of the devs in other software projects just give up and drop support of elcap
-
@cisebo6015 I my view, this is not about hate but to being properly informed. Devs do their job, a good one, indeed. However, as @MacTerrasa points out, we deserve at least to know if and why some given update is not going to work anymore with our systems; if there will be some other working in the future or they are dropping support for good. Nobody owes us nothing and hating is out of the question, but some kind of respect always helps.
-
@fredonmac Is that so?
-
@xyzzy said in 4.0.2312.24 crashes on ElCapitan 10.11.6:
FYI, the Vivaldi team has released an update that should fix this crash: https://vivaldi.com/blog/desktop/minor-update-3-for-vivaldi-desktop-browser-4-0/
@xyzzy thanks. but no support for 'propriety media' can you say what this means, even an example or two would do.
-
@bnmnesta 'Proprietary media' refers to Vivaldi's support for patent-encumbered codecs, such as H.264/AVC. These media types are special in that they are decoded using codecs that are part of macOS. Vivaldi users running on El Capitan will still be able to play most videos on YouTube but will run into playback issues on sites such as Twitter, Vimeo, etc. until a fix gets released, which hopefully will be included in the next 4.0-Stable update.
-
@carlos66ob Yes, it seems that .33 works fine, finally, in ElCapitan. Thanks!
-
-