How to trace what make vivaldi laggy (interface problem) and help devs to fix it?
-
After adding flags to enable debug the whole interface with default google instruments built-in Chromium, I found some fundamental issues which make whole interface lags.
Whole Vivaldi browser is a chrome window which running a site (yes, it's site) to display interface, and inside another div which running inside itself another site. That why everything so laggy. I think there is nothing that I can do except move to another product because of the problem too complex and will not be solved.
Only one way to make faster Vivaldi UI - drop current JS/HTML/CSS interface which renders browser by itself which than trying to render a site inside. Also, I tried to make a video with lags, but I have removed it because it will have no sense at all to prove something because no one will care or fix anything, because (sorry for many because) it's browser strategy and background on what everything is built.
-
The problem of Vivaldi is the use of exaggerated CPU in certain pages that does not happen in other browsers such as chromium.
It is not possible that devs can not see this. -
Ppafflick moved this topic from Vivaldi for Windows on
