History Panel enabling 1.7
-
I made a standalone installation of Vivaldi 1.7 stable to test this out. First I enabled "new history page" in experiments, then restarted, and I got a working history panel. This means with a clean profile the history panel works on Vivaldi stable, just as in the latest snapshot.
@craftbrewmaster If it doesn't work for you (because you don't have a clean profile), you can try and delete the "Local App Settings" folder in vivaldi/default. This did the trick for me in the snapshot.
Edit: Screenshot for proof
-
@luetage said in History Panel enabling 1.7:
I made a standalone installation of Vivaldi 1.7 stable to test this out. First I enabled "new history page" in experiments, then restarted, and I got a working history panel. This means with a clean profile the history panel works on Vivaldi stable, just as in the latest snapshot.
@craftbrewmaster If it doesn't work for you (because you don't have a clean profile), you can try and delete the "Local App Settings" folder in vivaldi/default. This did the trick for me in the snapshot.
Edit: Screenshot for proof
So I'm guessing that when I delete the Local App Settings, I'm going to lose not only all the settings that I've modified, but, like all the cookie exceptions I've created as well as the custom theme.
Honestly, it's not the redoing of the Vivaldi settings that is a major issue for me. But I have Vivaldi set to not accept any cookies, but I have gone through and created ~300-400 domain level exceptions where cookies are accepted. I also have javascript turned off, with another ~100 exceptions for javascript. Since there isn't a UI for easily exporting and importing those settings, blowing away my local profile isn't something I really want to do just to get the History Panel. I mean, I want it, it sounds great. But that's a lot of work to back through and enter all the [*.]domain.com cookie exceptions by hand.
-
@luetage - I see. I will not be recommending to folks that they clean their profile, in order to get access to a feature which is not yet ready for prime time. Folks can do it if they wish, but I won't recommend it.
-
@pafflick said in History Panel enabling 1.7:
@sophos02 I've blocked the Flash content internally (on chrome://settings/content) and added only a few exceptions to the white-list so that disabling the plugin doesn't really bother me...
That's what i also normally do but after talking to some tech support i found that there is at least one website where HTML5 is only exposed when flash is deactivated completely. Otherwise it will ask for flash to be activated...
-
@luetage exact same issues here (Win10).
After reading the thread, I deleted the local app settings directory - history panel appears. Then I restored the old settings again since I didn't fancy re-doing all the UI tweaks etc. - history panel disappears.
Hopefully this is something that will self-update in a later release without having to delete any settings files!
-
@mossman History panel appeared after installing snapshot 1.8.755.3...
-
@mossman Yeah, it's only an issue for people on stable at this point, guess they have to wait for a month if it doesn't work out of the box for them (and they don't want to meddle with it).
-
@luetage said in History Panel enabling 1.7:
@mossman Yeah, it's only an issue for people on stable at this point, guess they have to wait for a month if it doesn't work out of the box for them (and they don't want to meddle with it).
I do want to stay on stable, and don't mind doing a little work to get it to show. But my use case is a bit different than others. And if resetting my profile is going to blow away my cookie exceptions, I don't want to spend hours manually restoring ~400 domain level exceptions to allow cookies.
I have Vivaldi set to never accept cookies, and for certain sites I just put a [*.]domain.com exception to accept them. But there is currently no way to export/import that list to my knowledge. So after having done all that work initially, I'm weary of doing something that would recreate hours of manual data entry for myself.
If there was another way to get it working, or better yet a way to export my cookie exceptions list and import after resetting, I wouldn't mind manually going through the basic Vivaldi settings manually. That'll only take 10 minutes or so.
-
This post is deleted! -
@craftbrewmaster Are you even sure that your exceptions get deleted? You can always backup the folder you are about to delete and copy it back in if you lose them. Only do editing of the files with Vivaldi closed btw.
Another option is to use an extension to handle exceptions (with import/export) like vanilla cookie manager.
-
@craftbrewmaster Install the latest snapshot as a Standalone version, then it won't mess with your Stable version. Just use a different shortcut to launch it.
-
@luetage said in History Panel enabling 1.7:
@craftbrewmaster Are you even sure that your exceptions get deleted? You can always backup the folder you are about to delete and copy it back in if you lose them. Only do editing of the files with Vivaldi closed btw.
Another option is to use an extension to handle exceptions (with import/export) like vanilla cookie manager.
Not certain, but not worth the risk either. Another few weeks ain't that long to wait for the new feature. I looked at Vanilla Cookie Manager awhile back, I'm not sure if things have changed but I don't believe it handles what I need it to do. It handles actual cookies, rather than cookie exceptions.
@Pesala said in History Panel enabling 1.7:
@craftbrewmaster Install the latest snapshot as a Standalone version, then it won't mess with your Stable version. Just use a different shortcut to launch it.
Nah, I don't need a copy of Vivaldi running side-by-side. I've got too many browsers installed currently as it is. Of course doing that wouldn't even work to show me my history, because it's a separate browser. I'd prefer to stay on stable releases for a reason. I've done the whole beta tester thing for far too long, and keeping this system on more stable software is my preference. It's not a huge deal, but it is broken in my release; it's also an experimental feature, and that's probably why it's not moved into the normal stream of settings, there are still bugs to be worked out.
Please don't take this as knocking Vivaldi, I love it, and it's become my default browser. Looking forward to all the new features as they get implemented in the main code branch.