Shields should provide a way to persist state across tabs #4953
Assignees
Labels
feature/shields/panel
Front-end design and functionality of the Shields panel.
QA/No
release-notes/exclude
Milestone
Comments
cezaraugusto
added
the
feature/shields/panel
32 tasks
cezaraugusto
added a commit
to brave/brave-core
that referenced
this issue
Jul 5, 2019
close brave/brave-browser#4953 Shields state needed across windows/tabs is not stored in localStorage API. This follows the webUI convention for persistent state. Goal is to provide a way to handle upcoming changes such as onboarding screen and simple/advanced view setting. Other state such as stats, resources blocked, and blocking preferences are still handled by the back-end and are left untouched.
cezaraugusto
added a commit
to brave/brave-core
that referenced
this issue
Jul 9, 2019
close brave/brave-browser#4953 Shields state needed across windows/tabs is not stored in localStorage API. This follows the webUI convention for persistent state. Goal is to provide a way to handle upcoming changes such as onboarding screen and simple/advanced view setting. Other state such as stats, resources blocked, and blocking preferences are still handled by the back-end and are left untouched.
tmancey
pushed a commit
that referenced
this issue
Apr 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Persistent state only happens in the C++ back-end. Shields should provide a storage mechanism to handle persistent/non-critical state such as on-boarding, simple/advanced views, high-level user preferences, and shared state.
The text was updated successfully, but these errors were encountered: