Skip to content
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

Never remember history setting hides Bookie button #23

Open
baldurmen opened this issue May 6, 2014 · 3 comments
Open

Never remember history setting hides Bookie button #23

baldurmen opened this issue May 6, 2014 · 3 comments

Comments

@baldurmen
Copy link

Well, title says it all.

I deleted my whole profile (it was a bit corrupted anyway) and added all my add-ons one by one to finally realise that it's that &?&(* setting's fault.

To me it's a deal breaker. I won't use Bookie until this is fixed. But keep up the good job :D

@mitechie
Copy link
Member

mitechie commented May 6, 2014

Wow, thanks for the report. I've no idea off the top of my head why this is, but we'll look into it. It's probably something we're doing in ignorance as there's nothing nefarious there about it. I wonder if our use of localstorage to tell you about bookmarks you've bookmarked before with the little + sign is the cause.

Thanks for the diligent debugging of the issue. I can replicate it and we'll try to find a fix for it.

@mitechie
Copy link
Member

mitechie commented May 6, 2014

I will also suggest that you can use Bookie with the bookmarklet. If you go to your account page it provides a drag/drop bookmarklet. That will land you on the New Bookmark url in the web app and will still provide the useful features like tag suggestions and such. I'd just hate to have you not use Bookie at all while we get this sorted out. 😄

@widox
Copy link
Member

widox commented Nov 8, 2014

Doing a bit of poking at this, it appears that if we require the private-browsing permission then the extension would work with this setting on. It effectivly makes the browser behave as if you were in private browing mode all the time.

@mitechie did a quick test using this locally, and it does seem to work. wondering if we need to think about this more though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants