News for hackers. Stuff that matters.
Re:Show HN: Gurn – Use words, not bookmarks by Nadya on Thursday July 05, 2018 @07:35PM (#17467787)
Adding a keyword used to be more prominent and easy to do - you could right click any search bar and "Add as Keyword" - or you could edit the Bookmark link manually when bookmarking a page. They "simplified" bookmarking to where I need to navigate through several layers of menus to access the Bookmark Manager where I can finally edit the bookmark to add a Keyword and update the link to what it needs to be.

I have no idea why they made bookmarks so much more difficult to work with and I'm not sure when it happened - as I updated from FF39 to FF60. Using Quantum for the last few weeks - I'm pretty sure I'll be going back to FF39 as it's simply more usable. Especially since add-ons that were a large part of my workflow actually work (or even exist at all...)

Re:Show HN: Gurn – Use words, not bookmarks by chrismorgan on Thursday July 05, 2018 @08:10PM (#17467946)
“Add a Keyword for this Search…” is still there in the context menu.
Re:Show HN: Gurn – Use words, not bookmarks by Nadya on Friday July 06, 2018 @04:18PM (#17474779)
Checked on my work computer and you're right! Something must be going on with my userChrome.css back at home that's inadvertently hiding it from me, since I hide useless context menu options like "Set as Desktop Background...", "Email Image", etc. Something I'm hiding must be hiding "Add as a Keyword for this Search..." on accident.
Re:Show HN: Gurn – Use words, not bookmarks by chrismorgan on Saturday July 07, 2018 @01:30AM (#17477202)
And debugging those things can be nasty!

I wish :contains() had stayed in CSS Selectors Level 3, or that you could use XPath in stylesheets.

Hmm… #contentAreaContextMenu actually looks pretty sane. They all have IDs, which I really should have expected anyway. I’m going to add some rules to my own userChrome.css. Thanks for the idea!