Closed hayribakici closed 1 year ago
Thank you @hayribakici, appreciate you taking the time to implement this. I like this feature but I really don't want to add new permission just for this feature. New history
permission will open up this dialog to users and it is something I would like to avoid. Ideally, it should be done using the optional_permissions
.
I could not build this without installing @babel/plugin-proposal-class-properties
but maybe that's just me. The React component looks and works great but it is a class component and all of our code is using function components.
There are some other problems such as addresses appearing multiple times:
And many console log messages:
So I can't approve this right now, sorry.
hi,
thank you for reviewing the code and addressing the problems.
So using theoptional_permissions
, users can decide, if they want to permit the extension to have the history
-permission. So meaning, if they deny it, the extension should fall back to the regular input
?
Moreover, I tried to implement this feature regarding the functional components, however it quickly became a little messy, so outsourcing to its own class was the best option I could think of. Do you have any other ideas?
Reopened by #107, closing this PR.
Adresses #87 . This PR allows to users to add a page to the blocking list from the browser history.