-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import bookmark tags from the browser #63
Comments
Firefox doesn't yet let extensions access this data (they track this as bug 1225916) but perhaps will in the future. I'm not aware that chrome allows for tagging bookmarks via the browser UI. I half-plan to add an address bar button to the browser extension to allow people to at least edit the tags there without having to go to the site. The other (and main) feature of that would be making it more obvious that you're visiting a page that you've bookmarked. Maybe it could show you "$n comments" as well. |
An address bar button would be great. TBH I was only trying to add tags in Firefox to work around the bug with editing tags. Maybe should be changed to say something like AS A user I WANT be able to add bookmark tags within the browser SO THAT I don't need to create tags in the Quarchive website |
Agreed and done - will be a bit of a while until I broach the subject of an address bar button though I'm afraid! The bug with editing tags was corrected already :) |
Hi @calpaterson
Could you please confirm that tags are properly imported now? It would be a super feature, tags and Firefox are such a mess! |
I'm sorry, when I said "agreed and done" I wasn't referring to the work to complete this story. This will be one of the next things I work on though. |
Brief overview
AS A user
I WANT be able to add bookmark tags within the browser
SO THAT I don't need to create tags in the Quarchive website
AS A userI WANT bookmark tags to be imported from the browserSO THAT I don't need to create tags in the Quarchive website instead of in the browserAdditional details
The text was updated successfully, but these errors were encountered: