Skip to main content

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Emdek

@Mike, no idea about that then, cannot reproduce, with resuming it might be possible.
@Mike, but you didn't have to resume download to reproduce this issue, right?
@kwaku1, to co zostało tam podlinkowane nie zadziała bez przeróbek, o ile w ogóle działa.
No difference when testing it under XP, both files, they end with 100% and bytes number matches.
@Mike, still no luck, but it might be somehow XP specific too, I'll try to test it there too (testing that build under Windows 10 doesn't show any issues with values).
@Borut, @Otto Lutrinae, there are three options:
  • try version that comes in ZIP archive (as of now it is only missing H264, but it will be available later thanks to OpenH264 library), the one marked as ZIP package for Windows XP or later, 32 bit;
  • try experimental QtWebEngine build (this one is also missing H264, but probably permanently...);
  • install this to allow WMF to handle WebM:
Windows Media Foundation works in different way and so far I haven't seen any library that could take advantage of both legacy codecs and new system.
The main advantage of WMF is that it has built-in support for multiple formats, but sadly only proprietary stuff (plus it seems that full support is available only in Windows 10):

As noted earlier, GStreamer seems to be better choice but at the cost of extra package size (plus new infrastructure to build such packages with MSVC)...
@kwaku1, spoko, wersja dla XP powinna się trzymać jeszcze długo, a co do tamtej funkcji, to najlepiej śledź jej ticket:
@Otto Lutrinae, which build are you using?
There are two configurations available (not counting QtWebEngine), standard one uses native infrastructure available in Windows (Windows Media Foundation) and there is also -xp package, which uses GStreamer (and bundled codecs).
I'm already considering going just for GStreamer or at least replacing 32 bit variant (keeping support for XP, since it's "free") but it has some disadvantages, like increasing package size.
@Mike, dunno, I need some reproducible test case to find out what exactly went wrong.
@Mike, thanks for test link, unfortunately I was unable to reproduce it under both Windows and Linux.
@Oller, right, they have issues with parsing of plurals, at least when uploading source strings.
@rhubarbpieguy, that AppImage still can use OpenSSL 1.0 only, probably next one will contain extra variant of QtNetwork that is supposed to be compatible with 1.1.
@Borut, I've done some testing at it seems that all shortcuts (from default profile) are properly registered, but I still don't know what prevents them from firing when executed.
@ohno, can you reproduce that issue with about:blank?
You will have to disable Start Page first using about:config, by setting StartPage/EnableStartPage to "No".
Also please make screenshot showing sidebar of Inspector, showing computed background color.
@Mike, perhaps server sends invalid value for size of the file, hard to tell without some public test case.
Perhaps it's some change in QtNetwork, weekly 183 most likely uses older version.
@jasonliul, and it's only beginning of the final part of the journey to 1.0. ;-)
@ersi, sure, but it takes time with our limited resources. :-P
@ohno, that's unusual, which package are you using (win32 or win64)?
Does it happen with every page or just that one?
  • reworked toolbars:
    • added support for visibility toggle button (collapsing contents);
    • fixed unified toolbar and titlebar style under macOS;
    • toolbar visibility and location is now stored per main window;
  • improved sidebar(s):
    • added ability to add new sidebars;
    • allow to change their location by drag and drop;
  • vastly improved error pages:
    • special error pages are now used instead of SSL warning dialogs;
    • blocked content triggers dedicated error pages;
  • improved User Agents configuration;
  • added support for managing multiple proxy configurations and setting them per page or host;
  • reworked internal actions handling system allows to specify parameters for actions trigerred by keyboard shortcuts and mouse gestures;
  • vastly decreased import time for large bookmark files;
  • added module for listing opened windows and tabs;
  • improved styling under Windows, Unity and macOS;
  • added new default icon theme by Kamil Nęcek;
  • item views can now allocate extra space to predefined column other than last one;
  • added action to set, reset or toggle an option;
  • global editing actions now apply to focused single and multi line text edit widgets too;
  • added ability to drop URLs onto bookmark bars;
  • spell checking is now available in other multi line text edit widgets;
  • added action to control multimedia playback rate;
  • keyboard shortcuts are now validated while editing;
  • added support for customizing F12 menu;
  • implemented "Validate Using" menu;
  • added support for configurable Fast Forward rules;
  • lots of various fixes.

Please note, we haven't entered feature freeze phase yet, so 1.0 will see some more stuff, not just fixes and updates.
Next stop, (Pre) RC 2, next month.
@Oller, try contacting their support. perhaps they broke something...
That was a complete error message? Not really useful.
@ovas, it has less features than plus they used to have such feature around ten years ago and then they simply closed it, all files were lost...
@ovas, has technical difficulties, again...
@K@, great, no problem. :-)
@K@, according to bajasoft you most likely enabled all regional lists too, and this specific issue is most likely caused by Arabian profile.
@K@, uhm... Defaults in Otter Browser means no content blocking, you need to setup lists in Tools -> Content Blocking... first or set them per tab using button in Status Bar.