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

Update sensitive browsing designs to allow re-blurring of search results #2130

Closed
zackkrida opened this issue May 18, 2023 · 2 comments
Closed
Assignees
Labels
🕹 aspect: interface Concerns end-users' experience with the software design: needed Needs a designer's touch before implementation can begin ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend ⛔ status: blocked Blocked & therefore, not ready for work
Projects

Comments

@zackkrida
Copy link
Member

This is blocked until further user feedback or testing indicates it is necessary.

Problem

The sensitive browsing project proposal includes one feature not present in the design files. We discussed and decided to wait on this feature:

Users can unblur and reblur individual results through a simple and clear interaction on the search results page.

This means the desired flow for single results, as described in the plan, is something like this:

graph TB
    A(User searches) --> B(User views results w/ sensitive results)
    B --> C(User unblurs a sensitive result)
    C --> D(User can re-blur the result)  --> B
    C --> E(User visits the single result view) --> B
Loading

Description

We need to add this in the search results designs; perhaps with the 👁️ button in the bottom corner of results as indicated by Francisco previously.

Alternatives

Additional context

@zackkrida zackkrida added 🟨 priority: medium Not blocking but should be addressed soon ✨ goal: improvement Improvement to an existing user-facing feature 🕹 aspect: interface Concerns end-users' experience with the software ⛔ status: blocked Blocked & therefore, not ready for work design: needed Needs a designer's touch before implementation can begin labels May 18, 2023
@openverse-bot openverse-bot added this to Backlog in Openverse May 18, 2023
@dhruvkb
Copy link
Member

dhruvkb commented May 19, 2023

Aside to the discussion, that is an impeccable diagram 👨‍🍳👌. Nice to know that GitHub supports mermaid natively.

@fcoveram fcoveram self-assigned this Jun 21, 2023
@obulat obulat added the 🧱 stack: frontend Related to the Nuxt frontend label Jul 12, 2023
@zackkrida
Copy link
Member Author

Closing. Single results can be unblurred on the single result page, and will remain blurred when re-visiting the search results. I believe the current flow matches the mermaid chart here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software design: needed Needs a designer's touch before implementation can begin ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend ⛔ status: blocked Blocked & therefore, not ready for work
Projects
Archived in project
Openverse
  
Backlog
Development

No branches or pull requests

4 participants