Closed Bug 1061815 Opened 10 years ago Closed 10 years ago

[ALA][UI] Implementation of Panel 3 in appropriate context

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(feature-b2g:2.2+)

RESOLVED FIXED
feature-b2g 2.2+

People

(Reporter: marta, Assigned: marta)

References

Details

(Keywords: privacy)

Attachments

(2 files, 1 obsolete file)

Attached file ALA workflow (obsolete) —
Panel #3 allows to choose the Level of ALA. Once user clicks on "Adjust location" in panel #2, panel #3 is loaded, allowing the user to choose the granularity of the adjustments. The method used to choose the granularity is not yet defined (slider, radio buttons, list...). Anyway the choice should be confirmed and stored in the database with appropriate context (map:blur_level = 10). Refer to attachment for more information.
Keywords: privacy
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → All
Assignee: nobody → marta
QA Whiteboard: STATUS: waiting for UX decision, waiting for engineering decision
Priority: -- → P5
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
QA Whiteboard: STATUS: waiting for UX decision, waiting for engineering decision
Priority: P5 → --
Due to the changes in the UI we will in the end need panel #3. The panel should contain:
- depending on the choice from the drop down a different element should appear between the drop down and the “add exception” button
- If blur is chosen: show a slider with the options 500m, 1km, 2km, 5 km, 10 km, 15 km, 20 km, 50 km, 75 km, 100km, 500 km, 1000 km.
- If Custom location is chosen: show text and a button “set custom location” (no code)
- If Precise or No Location: show nothing
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
QA Whiteboard: STATUS: implementation work
Priority: -- → P5
Attachment #8482843 - Attachment is obsolete: true
Severity: normal → critical
Priority: P5 → P4
Can I suggest that the blur have fewer choices?  I think it makes sense to have 1km, 10km, 100km, 1000km.  From the user's standpoint, what's really the difference between 1km and 2km, or 50km and 75km?  I think it is too fine grained to be meaninful.
Let's discuss it during workshop. The granularity you proposed is too small IMHO. The difference between 1 and 2 km is based on usability wrt search apps. If I look for a restaurant but still want to blur my location, then I might be fine with walking additional km but not 2. 50/75 might make less sense but that was same idea from drivers perspective.
Severity: critical → normal
QA Whiteboard: STATUS: implementation work → STATUS: ready for review
Priority: P4 → --
Depends on: 1068008
Depends on: 1068023
Depends on: 1068031
Depends on: 1069144
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
feature-b2g: --- → 2.2+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: