The menus and contextMenus api does not work

[tstmax67]

Whenever I use the contextmenu api in glide.ts like this:

    await browser.menus.create({
      id: "example-item",
      title: "My Custom Action",
      contexts: ["link", "selection"]
    })
    await browser.menus.onClicked.addListener((info, tab) => {
      if (info.menuItemId === "example-item") {
        console.log("Clicked with selection:", info.selectionText);
      }
    })

or

    await browser.contextMenus.create({
      id: "example-item",
      title: "My Custom Action",
      contexts: ["link", "selection"]
    })
    await browser.contextMenus.onClicked.addListener((info, tab) => {
      if (info.menuItemId === "example-item") {
        console.log("Clicked with selection:", info.selectionText);
      }
    })

then save and reload the browser, I get this error:

And this happens with any website. Also trying to print browser.menus(or contextMenus) without await returns a promise as expected but trying the same with await/then produces error saying 'menus/contextMenus is not valid object'.

[suveshmoza]

You need to wrap it in a ConfigLoaded autocmd, top-level await don't work.

glide.autocmds.create("ConfigLoaded", async () => {
   browser.menus.create({
    id: "example-item",
    title: "My Custom Action",
    contexts: ["link", "selection"],
    onclick(info, tab) {
      console.log("Clicked with selection:", info.selectionText);
    },
  });
});

[tstmax67]

Is it possible to use glide functions inside onclick?

[hippi345]

re the follow up, yep. onclick is just a normal function from your config, same as a keymap callback, so glide.* is all in scope there. the config's browser object is the real extension api running in the main process, it's not a separate extension sandbox. e.g. using the selection from the click inside the page:

glide.autocmds.create("ConfigLoaded", async () => {
  browser.menus.create({
    id: "example-item",
    title: "My Custom Action",
    contexts: ["link", "selection"],
    async onclick(info, tab) {
      if (!tab?.id) return;
      await glide.content.execute((text: string) => {
        alert(`you picked: ${text}`);
      }, { tab_id: tab.id, args: [info.selectionText ?? ""] });
    },
  });
});

glide.excmds.execute("..."), glide.keys.send(...), glide.g etc. work the same way. just remember the function you pass to content.execute gets stringified, so pass stuff in with args instead of closing over it.