And we finally have it, first release marked as stable. :-) Not all planned features were finished in time, but hopefully at least some of them will make it into 1.1 later this year.
Changes since last RC:
some enhancements in experimental backend for QtWebEngine (Blink):
download dialog is now shown for tab that initiated it;
added support for handling requests to print page;
@exley, our build machine needed updates, and after updating one component it turns out that another also needs an update. :-/ Hopefully I'll be able to push remaining Windows packages tomorrow, 32 bit version was already built but not deployed yet.
@ersi, yes, but that had limited options, now it's closer to what others do in such cases. We show link specific actions only wen selection matches link structure, while that action is available for any selection.
@Quetzal, I guess that main issue is that macOS is still kind of exotic and very different from Windows and (to much lesser extent) Linux, I haven't properly tested any codecs there yet, since Apple seems to make it harder to support their platform, even MS finally went fully free with their SDK, while Apple has some totally not needed procedures to deal with...
That font issue sounds like QtWebKit issue or page feature which can be overwritten by setting bigger minimal font size.
@Quetzal, do you have issues with HTML5 player, flash player or both? Sadly, macOS port gets least love, which is ironic since WebKit is backed by Apple. Hopefully QtWebKit 5.212 alpha3 will bring some fixes.
@mad_king, ah, QtWebEngine, then it could be some lockup caused by calls that require synchronous replies but they are asynchronous in QtWebEngine. There were some recent changes that should prevent them, but 0.9.98 might instead be crashy at times with that backend (there is new workaround that allows to use global history but it needs some fixes for edge cases).
@mad_king, 0.9.94? First try updating to 0.9.98. It's QtWebKit backend? Which QtWebKit version (hopefully not the one bundled with Qt 5.7.1)? Also, is that any page or some specific one?
@smallhagrid, @Frenzie, that package is quite old, so if files weren't mixed or were mixed incorrectly (for example about dialog doesn't show proper version) then we might be facing some long gone issue.
@smallhagrid, to get extra codecs you should first unpack that build and unpack latest official release on top of it, overwriting most of the files.
Yeah, it would be a good idea to finally rebuild official package using OpenH264, but that takes time (customizing scripts and testing them), and now it would probably require pretty big update, since there were some incompatible changes in MXE scripts.
@Quetzal, could you please provide one of these links for testing purposes? Issues with resuming downloads in some cases are known, having some good test cases could help to finally solve them.
@Pref, it might be codecs issue, you might want to try xp build, this one has different set included or experimental QtWebEngine build (might be a bit crashy right now...), that one bundles own codecs too.
@browse op, I guess that we can reuse first post, later we can consider use of some wiki page or something like that. Important thing is to separately list stuff that depends on the backend (WebKit / Blink), since these should be forwarded directly to their maintainers.
