Snapshot 1.0.283.8 - Fixes to typed history, keyboard shortcuts for web panels and visual polishing
GinoPerla last edited by
be careful, all users, not just you. it seems it's related to permissions. I can't verify atm since I'm on Linux
GinoPerla last edited by
That's the problem ehhe
I can confirm for Gmail.
Any shortcuts I have are executed in parallel with text formatting.
I have changed bookmark panel to Ctrl+Shift+B, but would be nice if I'd be able to leave it as it is.
wardies last edited by
VB-5168 Additional “find” keyboard shortcuts broken: Changed find shortcut defaults on Windows and Linux
Yes! Shift+F3 now works as Find Previous in Page, thanks!
Now, about that regex Find option I was hoping for… There's a lot of space right next to the Match Case checkbox, isn't there?
Gmail for example.
Fendar last edited by
two lesser suggestions:
1. when typing something into the url-field the "up arrow" key should select the entry at the bottom of the suggestion list immediately. As of now the up arrow moves the cursor to the beginning of the url (which should be performed as usual my using the "home" (or "pos1") key). ATM the bottom most entry can be selected by pressing the "down" key first and then pressing the "up" key.
2. the suggestion list should vanish when the user clicks elsewhere. ATM I can only close the list by pressing "ESC".
KjokR last edited by
Some extensions do not seem to work, for example Momentum and Earth View from Chrome webstore.
npro last edited by
I know what Olli meant that's why I've said to change the color first which should be an easy task, then do whatever you want with the menu, or don't mess with it at all. But that color has to go asap imo.
justSQL last edited by
Would it be possible to shed any light on the problems you are facing? I understand that you want to be certain of the quality level, but what is the root cause of it taking so long? You want to be sure it's secure? Does it have significant performance issues? Is it simply not functional yet?
I understand if you don't want to (or can't!) comment on these things, though.
justSQL last edited by
I've had this issue in Opera, too. Opened 200 tabs in a private window quite fast, and the last few won't load anything at all. Just blank. I think that's a chromium issue. Not sure if using 64 bit builds would help (well, Opera doesn't offer them and I'm not running Vivaldi daily yet) but it certainly seems like a possibility.
On Linux, there is a package that includes proprietary codecs : chromium-codecs-ffmpeg-extra. It provides us with a ffmpeg built with support for h264 (and the rest). You can get it directly from the servers of Ubuntu : http://security.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-codecs-ffmpeg-extra_45.0.2454.85-0ubuntu0.14.04.1.1097_i386.deb
The link you give with crbug return a 404.
For the codec list, since the change to ffmpeg, V return a different result to the JS test HTMLMediaElement.canPlayType(). It responded before with an empty string which was understood as "No", while now, they respond with a "Maybe", which is wrongly interpreted by Youtube as a "Yes".
So the main issue is that no further tests are done by YT when they see a "Maybe" (but they should do them), and that they don't fall back to webm/flash.
They don't misadvertise the codecs list. "Maybe" is a good description, as they don't know. The issue come from the websites not following the specs.
The ffmpeg.so on my site work on any distro, yes. It's not cleared up because there is still a small doubt, but they should. Their only dependancies are libm.so.6, libz.so.1, librt.so.1, libpthread.so.0, libc.so.6. All of which are also dependancies of Vivaldi, so there is no issues here.
As for the part of the replacing FFmpeg, there are a lot of issues here, including legals ones, for not delivering the full (h264 inclusive) ffmpeg lib.
If you want to write directly to me, you can by using my pseudo @gmail.com
3630 last edited by
Nope, doesn't work. 'all users' is greyed out. When I change the folder to, for example 'desktop' then Vivaldi changes it to 'program files/vivaldi'. After that I can change to all users, but the problem persists. Should have something to do with permissions in windows 10, but can't find out what.
Xypher last edited by
BUG: Some Web Panel favicons still does not appear or load properly or none at all. eg. m.facebook.com and others…
BUG2: VB-9434. -> annoying bug on Mac.
Please make messenger.com scale properly as a Web Panel. Or at least make it possible to resize individual panels so it's not a one size for all thing.
Thanks for the release!
derDay last edited by
is the amazon wishlist button a bookmarklet? It doesn't work
(you can "install" it but it opens a blank new tab, when you want to use it)
Found it: VB-9113
Also I have opened a topic about it: https://vivaldi.net/en-US/forum/all/6326-would-you-please-add-bookmarklet-support
Known. Being worked on.
lewellyn last edited by
Unfortunately, my knowledge is apparently insufficient here. I am totally unable to get Chromium built with H.264 support (I can't get the boxes on the YouTube page to check themselves, like they do in the new Vivaldi snapshot).
Additionally, I have tried building FFmpeg with H.264 support from Chromium's tree. It works identically to Vivaldi's shipped FFmpeg (read: many unviewable videos) when the build is branded as "Chromium" and it crashes the tab for many video-containing pages when built as "Chrome" (read: the H.264 support seems broken, but Vivaldi doesn't ship with debugging symbols to try to figure out what's actually going on). However, with some patience, YouTube videos will start playing without audio this way.
This feels more and more like a Vivaldi issue, the more I poke at it. It may be saying "maybe", but I can't get the failing pages in my current test suite to show a MEDIA_ERR_SRC_NOT_SUPPORTED or similar in the Developer Console. This would be a prerequisite for falling back to another media type. If the page can't tell why the video is failing, it's just going to fail, which seems to be what we're seeing now with YouTube and others not loading the alternative representations we would have received in the previous snapshot. "Maybe" doesn't work when the page does not know that a source is unsupported. Even the fairly robust Kaltura player fails now: http://player.kaltura.com/docs/
As this seems unresolvable by the community (unless someone else takes the initiative to figure out WHY the Chromium FFmpeg branded as Chrome cause Vivaldi to fall over), I'd like to humbly request that the Vivaldi team reconsider advertising proprietary codec support (at least on Windows, and maybe OS until such time as it's actually possible for users to enable it, or Chromium bug 21318 ( http://crbug.com/21318 ) is resolved.
I'm also somewhat irritated that almost everyone I've gotten converted to Vivaldi is telling me now that " <insert video-playing="" site="">has stopped working! Help!" There is literally nothing useful I can tell them to make it work.
Cqoicebordel, it may be worthwhile to list that the .so you provide came from Ubuntu. IIRC, the Vivaldi RPM and DEB deliver binaries differing in required GLIBC versions, so the Chromium FFmpeg also may. As I'm not running it on Linux at the moment (as evidenced by having rebuilt Chromium on Windows a few dozen times in the past 24 hours…), I cannot verify that at this time. But it may save a non-Debian/Ubuntu user some grief if they can quickly identify a potential reason for "it doesn't work!" And I'm quite aware of the issues with providing a fully-enabled FFmpeg; I never offered a DLL, but I would have provided instructions as to how someone in a more legally-generous location could have built and used it if I was successful.
Maybe soon, I'll finally figure out how to see how a Debian package is built so I can build the same way on Windows, if they are doing something special. Of course, there may be a .spec (which is trivial to read) if I can find an SRPM of the replacement library...
For the record:
C:\...\chromium\src> python build\gyp_chromium.py --depth . -Dcomponent=shared_library -Dffmpeg_branding=Chrome -Dtarget_arch=x64 -Dproprietary_codecs=1 C:\...\chromium\src> ninja -C out/Release_x64 ffmpeg
But that yields an ffmpeg.dll that Vivaldi hates, but it seems like it should work fine. YouTube eventually plays without sound and many tabs will crash, even if it's obvious they have embedded media. Not necessarily an improvement over videos simply not playing. (For the record, an X86 build goes directly into out/Release. The 32-bit result is untested by me as I only have 64-bit Vivaldi readily accessible right now.)</insert>
Thank you for so much nice work again. It's a huge job and when I look through the setting page I can see how much you have done already. So much remains to do … so hang in there and keep up the good work!
But I have one small complaint; thanks to your memory management improvements I am now back to my old sin of having way too many tabs open at once :-(.