Closed Bug 848478 Opened 13 years ago Closed 13 years ago

[B2G][Calendar][Event] When creating an event the user is unable to scroll the window with the keyboard up which causes some input fields to be inaccessible.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 832261

People

(Reporter: jzimbrick, Unassigned)

Details

(Keywords: smoketest, Whiteboard: ux-tracking)

Attachments

(3 files)

Repro Steps: 1. Update Unagi device to build 20130306070201. 2. Launch the calendar app. 3. Press the + in the top right corner to add an event. 4. On the event screen tap on the "Title" or "Where?" input fields to bring up the keyboard. 5. Observe that the keyboard blocks the lower half of the event screen and the user is unable to access the "Notes" field without first opening and closing one of the date or time fields. Actual Results: User is unable to scroll the input window on the Create Event screen when the keyboard is up, blocking input fields. Expected Results: The user is able to scroll the Create Event window when the keyboard is up, allowing access to all input fields. Notes: The same happens if the user selects the "Notes" field first, blocking the top two fields. The only way for the user to access blocked fields is top open one of the date or time fields. This issue was found on an Unagi device running the following build: Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/bccf111e9131 Gaia: 77fb74ebf3bea340be9f8f4b4c9ac9dd7c12ab0b Build: 20130306070201
Component: Gaia::Calendar → Gaia::Keyboard
QA Contact: jsmith → wachen
Tapping anywhere to the left or right (not on an input element) will cause the keyboard disappear... We can and should handle this more gracefully by adding some extra height when the keyboard is shown to allow scrolling (or some similar technique)
Two fixes: 1) Content area should always remain scrollable, even when keyboard is up 2) Keyboard should never cover the active field. Content should automatically scroll itself to place the active field within the viewable real estate. This seems to work in other apps, so I'm assuming it's a Calendar issue and marking accordingly.
Component: Gaia::Keyboard → Gaia::Calendar
Whiteboard: u=user c=calendar s=ux-most-wanted
(In reply to Josh Carpenter [:jcarpenter] from comment #3) > Two fixes: > > 1) Content area should always remain scrollable, even when keyboard is up > 2) Keyboard should never cover the active field. Content should > automatically scroll itself to place the active field within the viewable > real estate. > > This seems to work in other apps, so I'm assuming it's a Calendar issue and > marking accordingly. Not exactly. Just because it works in other apps doesn't deem the issue as belonging particular to that app. Many different elements affect how the keyboard works - is the element position:fixed? How is the DOM setup? etc. Unless James thinks otherwise, I pretty strongly think this is a keyboard bug under a specific HTML/CSS setup.
Component: Gaia::Calendar → Gaia::Keyboard
Now that event reminders have been added, perhaps this bug should simply be changed to adding a scroll bar to the edit event screen in general. Once the user has added 3 "Remind me" times, the notes section is not able to be reached at all. Found with an Unagi device on the following build: Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/af9270e8f205 Gaia: a78ebf426840b5ef08c0cc3e437ad30aba3e2528 Build: 20130318070202
There's a different bug filed on what you've described in comment 5 - bug 852159.
blocking-b2g: --- → leo?
Moving back to calendar. It is a calendar issue and could potentially be a dup of bug 832261
Component: Gaia::Keyboard → Gaia::Calculator
Component: Gaia::Calculator → Gaia::Calendar
This is a dupe of bug 832261. Collapsing this down to one bug.
Status: NEW → RESOLVED
blocking-b2g: leo? → ---
Closed: 13 years ago
Resolution: --- → DUPLICATE
Verified as a Duplicate of 832261
Status: RESOLVED → VERIFIED
Whiteboard: u=user c=calendar s=ux-most-wanted → ux-tracking
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: