VivaldiHooks - more useful mods!

Steffie

@potmeklecbohdan said in VivaldiHooks - more useful mods!:

expect everyone to be at least a bit programming-literate

Gulp!

Sweat...

nomadic

@potmeklecbohdan said in VivaldiHooks - more useful mods!:

I somehow expect everyone to be at least a bit programming-literate

Even at an engineering school, programming talk makes people's eyes glaze over.

Being one of the few people with coding experience in an embedded control class is ~~not~~ fun.

den_po

@Pathduck said in VivaldiHooks - more useful mods!:

@den_po I've noticed that VivaldiHooks causes issues with the Guest Profile

That is an interesting one. Even the simplest solution doesn't look easy to implement at the first glance. Gotta think about it.

@valiowk said in VivaldiHooks - more useful mods!:

Could someone help confirm whether autocomplete-domain.js has the following problem:

I've pushed a workaround. Please check it.

Pathduck

@den_po Thanks for the reply.

I've temporarily fixed it by setting defaultLoad: false in in jdhooks.js (as discussed above) but will have to re-apply it for every update obviously. What does "defaultLoad" actually do?

Everything else seems to still work as expected, and hooks appear to not load in Guest. They still load in a Private window as expected.

A Former User

@Pathduck said:

What does "defaultLoad" actually do?

See start of this page (if you don’t have pagination on 20 posts, start at post 161).

Each time Vivaldi starts, the main hooks file checks for files under hooks/ and makes notes about them to your storage (that is per-profile, this is why it’s fine in both guest (another profile) and private (same profile) window). Some of the files are already known (i.e. entries for them are present in the storage) so their state is how you set it before. Some are not known (i.e. you added the files since the last check) and these are either all activated or all deactivated, depending on defaultLoad.

valiowk

@den_po Thank you very much!

iAN CooG

Warning: a bug with speeddial-downloads.js with the latest snapshot 3.3.2001.3

After updating I noticed speeddial-downloads.js cause the new tab speed dial to only show the splashscreen. Not a Vivaldi bug but I reported it on github aswell
https://github.com/justdanpo/VivaldiHooks/issues/41

Steffie

@iAN-CooG said in VivaldiHooks - more useful mods!:

speeddial-downloads.js

Oh! I don't have that one, so i suppose that means that my version of Hooks is obsolete. I never remember to periodically check its homepage "just in case" a new version arrived.

Pathduck

@den_po Just a FYI I noticed that Quick Commands broke in Vivaldi 3.3 with qc-close-tabs activated. Fortunately installing the latest commit seems to have fixed it.

Tried to go through the commits to see what might have been fixed, but qc-close-tabs was last updated 3 months ago, so the fix must've been in the v3.3.2001.3 commit? Lucky fix?

Anyway, all working now

iAN CooG

New jdhooks.js solved the issue, good work

nomadic

Finally made my first Hook!

Still have a ways to go in my understanding of how it works, but even a small step forward is something.

@nomadic said in (Help) Button to hide vertical tabbar?:

Hadden89 luetage There is the option of using VivaldiHooks to trigger inbuilt Vivaldi commands.

I am far from an expert at writing a hook mod, but looking at panel-right-toggle-button.js and bookmarks-button.js as examples and setting a breakpoint to see the function that was called on toggling the tab bar, I made this:
//Toggle tab button before AddressBar
{
  function toggleTabsOnClick() {
    const WindowActions = vivaldi.jdhooks.require("WindowActions");
    WindowActions.toggleTabs(window.vivaldiWindowId);
  }

  vivaldi.jdhooks.hookClass("toolbars_Toolbar", (origClass) => {
    const React = vivaldi.jdhooks.require("React");
    const SettingsPaths = vivaldi.jdhooks.require("_PrefKeys");
    const ToolbarButton = vivaldi.jdhooks.require("toolbars_ToolbarButton");

    return class extends origClass {
      render() {
        let ret = super.render();
        if (this.props.name == SettingsPaths.kToolbarsNavigation) {
          ret.props.children.push(
            React.createElement(ToolbarButton, {
              tooltip: "Toggle Tab Bar",
              onClick: toggleTabsOnClick,
              image: vivaldi.jdhooks.require("_svg_tabs_large"),
            })
          );
        }
        return ret;
      }
    };
  });
}
There is probably a better way to do it, but if you want a button that toggles the tab bar, this works.

Pathduck

VivaldiHooks seems to break new profiles including using a clean --user-data-dir. Just leads to a an empty URL.

https://github.com/justdanpo/VivaldiHooks/issues/43

Crimsonshade

Since 3.4.2066.70, qc-close-tab.js appears to be breaking Quick Commands entirely. Any time I have it enabled, Quick Commands stops working and just presents this error:
Quick Commands Crash.PNG
This is still the case as of the most recent snapshot. I originally reported this as a Vivaldi issue [VB-73195], but have now determined it to not be a Vivaldi bug and have isolated the cause to this one mod. Disabling qc-close-tab.js and restarting the browser makes Quick Commands work again.

Steffie

@Crimsonshade Thank you SO MUCH for this! Eureka. I have had no idea why for several weeks or more, my mouse-gesture to open Quick Commands resulted in no QC popup & instead a weird error bar along the bottom of the page. Now that i disabled this one & relaunched, it's good again. Hugs to you!

Pathduck

@Steffie Have you guys updated VivaldiHooks from the git lately?

luetage

@Crimsonshade You should never report bugs before testing with clean profile without any modifications running. Posting a topic about a bug you found and then waiting for someone to confirm it before reporting it, is also a very good idea. The way you did it will just cost someone else time, which hurts every user in the long run, because that time could be spent more productively.

I mean it’s not like this is a tragedy , but just post about it on the forum first next time.

On a somewhat related note: I think they changed the Vivaldi internal command from “Report a bug” to “Report a bug on the forum”. They might have their reasons…

Steffie

@Pathduck said in VivaldiHooks - more useful mods!:

VivaldiHooks

Not a guy, but here's my response anyway :face_with_stuck-out_tongue_winking_eye:

I've not actually updated my VH for months, but every so often i go to the page to see if there's something new. Apart from just now for this post, i last did it a few weeks back, when then as now it is still only this:

Given i do not use that one anyway, i have continued with my VH version installed several months back.

Pathduck

OK then. You Sheilas. Better?
Or maybe "y'all"? Too country ? "You folks"?

Anyway, just saying it might be an idea to do a git pull and reapply the hooks by running installhooks just to be sure.

QC still works for me on Win10 even with the QC hook enabled. Although the actual function of the hook, being able to close tabs from the QC no longer seems to work as it should... I'll report that to @den_po on Github.

Crimsonshade

@luetage Tbh I only reported the bug because the dialogue suggested I should; and I was pretty frazzled after a long day at work that day. It was only a few days later, when I was a bit less stressed and encountered the bug again, that I took time to investigate the cause.

EDIT: I should perhaps also add that I rarely if ever use the Quick Commands feature anyway, so I had no point of reference to begin with.

Steffie

@Pathduck said in VivaldiHooks - more useful mods!:

You Sheilas. Better?

It is much better, & i encourage you + everyone else to now adopt this instead of That Other One.

I can't foresee much blowback...

@Pathduck said in VivaldiHooks - more useful mods!:

might be an idea to do a git pull and reapply the hooks by running installhooks just to be sure

Clearly you get git much more than i do, so i ask this not as a Doubting Tomasina, but more as someone simply clueless -- if the dates published per my pic say that there's been no updates for x months, can i not just rely on that? Is it possible something new has been pushed there but the dates never updated to match? Definitely for a long time now, i have been simply trusting those dates when deciding to update or not.