Closed Bug 813120 Opened 13 years ago Closed 13 years ago

[FTU] choosing the time zone is inconsistent

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect, P1)

x86_64
Linux
defect

Tracking

(blocking-basecamp:+)

RESOLVED WORKSFORME
B2G C2 (20nov-10dec)
blocking-basecamp +

People

(Reporter: julienw, Assigned: kaze)

References

Details

* have the ftu launching (eg after a "make reset-gaia") * hit "next" until you land on the "Date & time" page => GMT +00:00 is displayed * hit "change" => The selected timezone is GMT -08:00 This is inconsistent.
Assignee: nobody → fernando.campo
Component: Gaia → Gaia::System::First Time Experience
blocking-basecamp: --- → ?
blocking-basecamp: ? → +
Priority: -- → P1
Target Milestone: --- → B2G C2 (20nov-10dec)
Dear all, The root cause for this issue is, The default selected option would be GMT -8, and if you select it again, it would not trigger change event (correct behavior) to let FTU app change the shown text. I think the easy fix for this issue is, (See apps/communications/ftu/index.html) 1. Just change default text in <p id="timezone-configuration-label">GMT +00:00</p> 2. or mark <option value="0">GMT +00:00</option> as selected. However, in an offline discussion, another concern is that the current time zone list in FTU is different from that in settings app. We may need to address that as well. Thanks.
I'd choose option 2. (but I'm not a UX designer).
Let me explain : I'd choose option 2 because then all options in the select box are evenly distributed around the default option. However, this may also be set depending on the language that was chosen in the previous panel. For example, for Brazil, the most used timezone would be GMT-3 so this might be a sensible default option as well.
Flags: needinfo?(jcarpenter)
Hi all, I'm currently working on this, and my first approach was also to mark GMT +0:00 as selected by default, but I encountered some problems when doing that: - right now is not possible to scroll the selection screen so we can have the selected option visible. For doing this we would have to choose an arbitrary value and hardcode it, or change the corresponding building block so we would have some anchors that we can use to scroll to - as rudy pointed out, the current behaviour of FTU and settings time zone is different, and both of them have weird details that makes them quite not user friendly. There will be a conversation later today between interaction/designers to try to solve this. You can follow the discussion about this on bug #810386 So right now I can do couple of things: - make a PR solving the default selected issue (without the scroll), knowing that is a workaround from the real problem, and possibly temporal (if time zone selection is changing) - create a new bug to fix the building block (system issue) to create some anchors so we can scroll to position - block this bug till #810386 is solved I'm gonna get Ayman into this so he's aware of the paralel conversation
Flags: needinfo?(aymanmaat)
Depends on: 810386
Bug 810386 is now fixed, and we’re using the standard continent/city selection paradigm now. So this bug, as reported by Julien, does not exist any more. If the continent/city selection is not what you prefer, this can be rather easily modified with the new /shared/resources/tz.json file.
Assignee: fernando.campo → kaze
Works now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(jcarpenter)
Flags: needinfo?(aymanmaat) → needinfo?
Flags: needinfo?
You need to log in before you can comment on or make changes to this bug.