Chromium 70 update – Vivaldi Browser snapshot 1322.4
-
[Regression] Mouse gestures stop working after cycling tabs via the mouse wheel (VB-44219)
that was nasty, now seems working again -
third!
-
Undocument fix? Moving a tab stack on a 2nd window back to the main window doesn't crash Vivaldi anymore for me.
EDIT: Nevermind, I forgot it affects tiled tab stacks, not normal stacks. Still crashes when moving back a titled tab stack to 1st window. -
Tiling 3 tabs to grid is broken (VB-43198)
This works, but not as expected. IIRC tiling three tiles to a grid before would use half the window for one tile, and the other half for the remain two (tiled horizontally).
Now it uses one third of the window for one tile, and two thirds for the remaining two (tiled horizontally).
It is a moot point which method is better.
Tiling four tabs, then closing one after the regression gave the result that we used to have before the regression arose. Now, instead of a grid layout, the three remaining tiles are tiled vertically.
-
Changes to chrome://flags after the engine update, if you're interested. Note that some flags may be chrome specific and most of them are only useful to developers. Always disable flags to see if they're causing any bugs before reporting.
New:
- #enable-webrtc-hybrid-agc
- #new-password-form-parsing-for-saving
- #enable-resource-loading-hints
- #document-passive-wheel-event-listeners
- #enable-surfaces-for-videos-ms
- #enable-autofill-save-card-sign-in-after-local-save
- #omnibox-drive-suggestions
- #enable-service-worker-long-running-message
- #enable-web-authentication-cable-support
- #force-unified-consent-bump
- #enable-query-in-omnibox
- #autofill-preview-style
- #enable-lazy-image-loading
- #autofill-primary-info-style
- #autofill-enable-company-name
- #autofill-no-local-save-on-upload-success
- #enable-sync-uss-bookmarks
- #enable-lookalike-url-navigation-suggestions
- #sync-standalone-transport
- #sync-USS-autofill-wallet-data
- #enable-resampling-input-events
- #enable-resampling-scroll-events
- #autofill-dropdown-layout
- #happiness-tarcking-surveys-for-desktop
- #enable-service-worker-imported-script-update-check
- #sync-support-secondary-account
Changes:
- #committed-interstitials > #ssl-committed-interstitials
- #enable-site-per-process and #site-isolation-trial-opt-out are changed with a better description of how it is set
- #stop-in-background > #stop-non-timers-in-background
Removed:
- #enable-scroll-prediction
- #warn-before-quitting
- #enable-token-binding
- #secondary-ui-md
- #one-google-bar-on-local-ntp
-
@npro: Uhm, no.
-
Is it just me, or does the
vivaldi://about
page got a subtle facelift? -
@ian-coog: After a few minutes of using the snapshot, this does seem to be fixed. Hopefully it stays fixed for here on out. Vivaldi without mouse gestures is painful.
-
@pafflick Font size or something else I didn't notice?
-
@pafflick: Which one? It seems that typing vivaldi://about redirects to chrome://about, which is displayed as vivaldi://about in the address bar.
Using the help menu to go to vivaldi://about looks (as far as I can tell) roughly the same.
-
@christoph142: oh yes
-
Wow! Mouse gestures and switching tabs by wheel now work really better. And switching even works when a page is loading.
Only one bug requires fix still - context menu opens after switching tab done (important condition: 'Show tab Cycler' option should be disabled.
Mod Edit: Image posted inline.
-
Wow, what a huge performance increase. Websites load much faster on macOS 10.14. Is this caused by the Chromium update?
Great job guys -
@ornorm Go ahead, find the differences:
-
@lonm said in Chromium 70 update – Vivaldi Browser snapshot 1322.4:
It seems that typing vivaldi://about redirects to chrome://about, which is displayed as vivaldi://about in the address bar.
It never happened to me, I always got the same page either by typing this URL to the address bar or by clicking the respective menu item.
-
@pafflick That's very strange. I just tried it again, and
vivaldi://about
works correctly now. I must have not been paying attention earlier. -
will 2.0 stable also can be updated to chrome70?
-
@lonm But still it's a mystery how you got there - especially that I use this page quite often, so I should've come across it too.
-
@rtransformation: No 2.0 will not use Chrom<em>ium</em> 70
-