@Steffie said in Periodic tab reload – Vivaldi Browser snapshot 2056.19:
Afaik , this initial version of this new feature is not sticky across relaunches [of the individual tabs, nor the browser].
Neither is the extension, if I remember correctly I've always had to reset the reload timer after restarting the browser. So it's nothing new. Even if that difference exists, it's such a minor issue that it wouldn't prevent me from removing the extension.
Actually, will the persistence of the reload timer across restarts be optional? I don't think I would want that to be my default behavior. Already, unless a tab is pinned, it shouldn't load upon restarting the browser until I activate the tab, with my configuration.
As I use lots of tabs, I don't want to slam the network and put the load on my browser at startup. I might be in a hurry to load one specific page, so it's better for me that way. Not having the periodic tab reload persist is sort of similar, though I understand why some want it, just as others might not like lazy loading of tabs.
Instead of tying the persistence of the periodic tab reload timer setting to a specific tab, I think it might make sense to tie it to a specific URL. Actually, instead of tying the reload timer at all to a tab, putting it on a URL or partial URL (including any URLs that begin with the defined URL) seems like a better design. It's not (typicallly) that people want a certain tab to automatically reload on an interval, rather certain pages regardless of the tab they are in.
If this hasn't already been requested, I'll write it up and post it in the feature requests category.
I cannot run the snapshot for some unknown reason on any computer
C:\Vivaldi Snap directory
Has worked forever before!!!
Either my method is wrong or the download is perhaps corrupt
Help anyone....thank you
@npro Teehee, i strongly endorse/support/concur.
I have stubbornly persisted on & off for the past few days to go through most of my large suite of regular fav sites, one by one tuning uBO to them. In most cases i was pleasantly surprised that i seemed able to control these sites nearly as well as with uM ... but there's now three of my favs that simply refuse to work as well in uBO as they do in uM. The granular matrix component control available in uM is simply superb.
Then, once i was done, i decided to take a sticky-beak at the comparative resource consumption. I assumed they would be more or less the same, hence i was pretty surprised to discover that as well as its surgically-precise tuning control [or more likely, exactly because of it], uM wiped the floor with uBO. Whilst i'm not, anyone running on limited hardware should like this uM advantage.
Though it's taken a fair bit of effort & a lot of time to reach this point, i'm actually pleased to have done it, because now i have a renewed quantified rationale to explain to myself, anytime in future that i start wondering anew why am i using uM rather than uBO.
There is only one thing for which uBO would be a better choice in Vivaldi than uM, for anybody who likes using a UI Zoom < 100% ... uBO's UI seems not to break as badly as uM's UI does.
When will the segment heap be supported? It's only a description of the manifest file, so support it with the following snapshot don't you?