This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Enhance browser toolbar #8474
Labels
eng:qa:verified
QA Verified
eng:ready
Ready for engineering
Feature:Browsing
Issues related to browsing experience, browser navigation, not web issues
feature request 🌟
New functionality and improvements
needs:triage
Issue needs triage
Comments
vesta0
added
feature request 🌟
New functionality and improvements
needs:UX-feedback
Needs UX Feedback
needs:triage
Issue needs triage
labels
Feb 18, 2020
vesta0
added
the
Feature:Browsing
Issues related to browsing experience, browser navigation, not web issues
label
Feb 19, 2020
4 tasks
this issue addresses some of the feedback around the blue dot notification #7408 |
topotropic
added
eng:ready
Ready for engineering
and removed
needs:UX-feedback
Needs UX Feedback
labels
Mar 5, 2020
mcarare
pushed a commit
to mcarare/fenix
that referenced
this issue
Mar 10, 2020
mcarare
pushed a commit
to mcarare/fenix
that referenced
this issue
Mar 10, 2020
mcarare
pushed a commit
to mcarare/fenix
that referenced
this issue
Mar 11, 2020
mcarare
pushed a commit
to mcarare/fenix
that referenced
this issue
Mar 11, 2020
mcarare
pushed a commit
to mcarare/fenix
that referenced
this issue
Mar 11, 2020
mcarare
pushed a commit
to mcarare/fenix
that referenced
this issue
Mar 11, 2020
ekager
pushed a commit
that referenced
this issue
Mar 11, 2020
ekager
pushed a commit
that referenced
this issue
Mar 11, 2020
Items removed and reordered, verified as fixed on Beta 4.1. (the top nav bar itmes order in the mock-ups is to be updated by @topotropic) |
severinrudie
pushed a commit
to severinrudie/fenix
that referenced
this issue
Mar 18, 2020
severinrudie
pushed a commit
to severinrudie/fenix
that referenced
this issue
Mar 18, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
eng:qa:verified
QA Verified
eng:ready
Ready for engineering
Feature:Browsing
Issues related to browsing experience, browser navigation, not web issues
feature request 🌟
New functionality and improvements
needs:triage
Issue needs triage
User Story
Acceptance Criteria
It looks like users find the current behaviour either confusing or irritating, and overall not useful. Highlights of some user feedback:
Some users assume blue dot is highlighting reader mode being either a new feature or notifying that we made changes to reader node. They expect the blue dot to go away after they interact with reader mode once, and they find it confusing when it doesn't.
Many sites can be viewed in reader mode which means the blue dot does appear very often. Many users find that irritating and annoying and it has caused some users to drop off (self-reports).
The frequency of showing the blue dot, also means that the blue dot is not accomplishing its objective of notifying users of the availability of reader mode, PWA, or open in app option, since users will begin to ignore it.
Page actions in a similar category are grouped together for easier interaction (add to collection, add to top sites, add to bookmarks, add to homescreen) so they are faster to locate and use.
Remove "Help" from browser toolbar as it is very rarely used.
UX designs
Updated Mar 5, 2020 by @topotropic
Site menu with the minimal amount of menu entries:
Site menu with site specific menu entries (like "Reader mode", "Open in app"):
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: