(In reply to megancutrofello from comment #31)
What if it only applied to developer/local addons? This way there's still SOME recourse for maintaining true bookmark keyword functionality, and I can code my own tool, which is somewhat similar to writing bookmarklets.
You can write experimental WebExtension APIs that basically do whatever you wish in Nightly and DevEdition, see https://firefox-source-docs.mozilla.org/toolkit/components/extensions/webextensions/basics.html#webextensions-experiments.
I definitely don't want
lol autocompleting to this page. Here's how
lol autocomplete currently looks: https://puu.sh/H4MnA.png
Normal urlbar matching can do a good job even without having to remember hundreds of keywords, why wouldn't you just type "lol something" and pick a result that is at a DOWN of distance?
(In reply to Claudius from comment #32)
Please tell that to @Mugurell and @kbrosnan on GitHub, who closed and even LOCKED that issue pointing at this one here: https://github.com/mozilla-mobile/fenix/issues/12099#issuecomment-704143064 so this is not just about desktop. It affects Firefox on Android, too.
That seems right, Android won't implement keywords if desktop plans to change or deprecate them. I'm just saying that Android development won't happen here.
(In reply to megancutrofello from comment #33)
Sorry, just to clarify my suggestion/request here, when I said preference, I meant something buried in about:config, so it would definitely be a power-users-only thing.
Malicious programs can easily flip prefs, or convince users to do it.
(In reply to jscher2000 from comment #34)
Currently, I can type my keyword and press Enter to load the bookmarked URL. This is a non-search use of a keyword. The strings are too common to select from history. Without the keyword, I would need to filter using * to find my bookmark.
I'm interested in this, what's wrong with * when you already know you're looking for a bookmark? Is it just that you figure out later that you were looking for a bookmark?
Unfortunately, the Bookmarks API doesn't include any feature to access the keywords
That's because we knew keywords were a huge hack on top of bookmarks, adding an API would have forced us to keep them like that.
Or, comparing the deprecation of Live Bookmarks, creating an export file (not .opml, but something) could be helpful.
Fwiw, the plan would be to convert keywords to custom search urls, though only for the ones containing %s.
But AFAICT, the first step will be to introduce custom search URLs, then we may do the conversion... and only later we can start looking at remaining keywords deprecation. There's still quite some time to think about a solution for those. MAybe they could remain as "nicknames" for bookmarks, but there's problem with that, because users forget about keywords they set, and then file bugs asking why typing "car" went to "dealercar.site" instead of searching "car".