For example setting keyword `t` for uri `data:text/plain,%S` and entering `t foo` into location bar will navigate you to `data:text/plain,foo`, i.e. "make document". If Google Docs have GET endpoint for creating documents, it should work. For searching you can apparenly use `https://docs.google.com/document/?q=%s`.
Even if you're adding it manually, I think the list of search engines is a more intuitive place to put such a feature than "bookmark keywords".
Compared to similar features in Chrome or DDG's bangs, Firefox's bookmark keywords seem less discoverable to me.
They're equally powerful. Automatically adding search engines means users don't have to do so by hand, but you can still manually create a "search engine" too (e.g. "https://xkcd.com/%s/" with the keyword "xkcd").
In Firefox I keep a folder with bookmarks that have keywords, but I would prefer the UI in Firefox's search engine settings (the bookmark manager doesn't have a keywords column).
The problem is few will discover Firefox's bookmark keywords unless they're told about the feature, and manually create such bookmarks, while Chrome automatically creates keywords for search engines and prompts users to try them out.
Just one reminder: in Firefox there is "Add a Keyword for this search..." command on any (form) input field that triggers keyword bookmark creation wizard [1], so what Chrome does automagically by visiting page with form (or using the form once?) you can do quite easily in Firefox as well, but you must find the input field, shift+f10 or click few times and pick keyword.
Also, using same keyword for different URL will (at this moment) silently "transfer" the keyword to new URL, with no warning about
[1] yet again, this wizard obscures resulting bookmarked URL with relevant `%s` part, so regular user cannot find out how this thing works. (I'm sad how hard recent browsers tend to hide whole concept of URL from users, in general. I understand it, but it's sad.)
[2] I had to `select moz_keywords.keyword, moz_places.url, moz_places.title from moz_keywords inner join moz_places on moz_places.id == moz_keywords.place_id order by keyword;` last time I wanted to see all my keywords. (And I'm trying to keep them in a single folder as well.)
My main worry is that I mainly use tags to sort my bookmarks before using folders, and even after many years they (tags) aren't showing up on mobile. I'm afraid they'll eventually pull tags support out and become way less useful.
Tags are IMO a better sorting system than folders.
It serves me well: using native bookmarks search accelerator [1] in url bar * , keywords and 'rating system' allows me to for example quickly pull "best personal blogs of people writing about javascript":
* *** javascript guru
I understand your worries, IIRC there used to be bookmark "description" field that was just recently removed (I've used it maybe twice) and if tags are globally used like this description was, your concern could be quite relevant. If need arises, perhaps some sqlite-fu could transfer tags to titles, at least.[1] https://support.mozilla.org/en-US/kb/address-bar-autocomplet... - this is FMPoV also quite underrated and unknown feature.
You ask why not improve opensearch markup, just like I have asked why not improve RSS. I am quite convinced that the RSS model has a lot of untapped potential for a distributed internet, but it also thwarts central control, surveillance, tracking etc.
If I'm reading that right, they're deprecating support for discoverable browser-independant markup for searches; and replacing it with the requirement that each site actively develop (and maintain!) a software plugin for every browser their users might want to use.
The whole point of a "user agent" was to go out and do things for me on the web; and the idealistic goal was that each person could choose an agent suited for them, which then had tools to programmatically discover and interact with the web in a common manner (reducing engineering load on the webdevs).
And I don't want to try and use a separate search tool (with new flashing graphics and ads!!!!) for every site I go to... I want a single search tool, like FF offers right now. (Aside: not to mention chrome's "auto-discovery of opensearch when you tab after typing a domain" is actually MORE useful than FF's manual mode!).
Taking a step back and removing support for a declarative api seems to me like the really wrong direction for an open web. Instead of sites supporting a single declarative browser-independent markup; they now have to deal with a long tail of (2-3 + who knows how many) browsers; and users with a niche browser have to spend effort convincing every site to support their browser.
Why not try to improve the opensearch markup instead?