Message / notification API

[HelmicNewciv]

Maybe I'm just not finding it, but it would be helpful to have some way to display a notification or message through the API. You can sorta do it by using glide.commandline.show but that's clearly set up for you to pick an option from a list rather than temporarily displaying, say, a visual confirmation that your mpv script is currently running (ie you hit the right button).

The notifications displayed up top may work, but ideally there should be options to have those notifications automatically dismiss (such as for quick confirmations). Coming from qutebrowser I'm already pretty used to notifications showing up where glide has its command line.

[idlip]

I just explored glide.d.ts file in ~/.config/glide and notice it has Notifications namespace wrapped.

async function notify(title: string, message: string, options?: Partial<browser.notifications.CreateNotificationOptions>) {
    return browser.notifications.create(undefined, {
        type: "basic",
        title,
        message,
        iconUrl: "chrome://branding/content/icon32.png",
        ...options,
    });
}

glide.excmds.create(
    { name: "notify_test", description: "Send test notification" },
    async () => notify("Glide", "manual trigger works")
);

glide.keymaps.set("normal", "<leader>n", "notify_test");

Glide might have more hidden gems to tweak. People should post more on #147 !!

[ian-h-chamberlain]

That's true, I think generally any web extension API should be usable: https://glide-browser.app/extensions
Browser extensions can do a lot when given the right permissions!

There are different kinds of notifications people might want too though. I have sometimes wanted to display a message like the top bar that appears when config fails to load, but as far as I can tell there's no way to show something custom except by throwing errors from an excmd / autocmd?

There are some nice customization options Glide uses internally that would be cool to expose (e.g. callbacks for custom buttons), although I'm not sure about the security implications:

glide/src/glide/browser/base/content/browser.mts

Lines 727 to 753 in cbaddd2

	add_notification(
	type: string,
	props: {
	priority: number;
	label: string | DocumentFragment;
	eventCallback?: (
	parameter: "removed" | "dismissed" | "disconnected",
	) => void;
	buttons?: GlobalBrowser.NotificationBox.Button[];
	},
	) {
	this.on_startup(() => {
	const { buttons, ...data } = props;
	gNotificationBox.appendNotification(
	type,
	data,
	buttons,
	// for the vast majority of our notifications, the click jacking delay just adds
	// visual noise and distraction as most of them will be triggered after say a keypress,
	// not when just browsing the web normally.
	//
	// of course this *could* stil happen, but I think the tradeoff is worth the risk of
	// some user potentially accidentally clicking a notification button.
	/* disable clickjacking */ true,
	);
	});
	}