Closed
Bug 850413
(skb)
Opened 11 years ago
Closed 11 years ago
Story - Repositioning content for skb display
Categories
(Tracking Graveyard :: Metro Operations, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jimm, Assigned: jimm)
References
Details
(Whiteboard: [forms] feature=story c=Content_features u=metro_firefox_user p=15 status=verified)
Attachments
(2 files)
144.99 KB,
patch
|
Details | Diff | Splinter Review | |
3.05 KB,
text/html
|
Details |
str: 1) click on a form input 2) (soft keyboard is displayed) note a white are shows up above the keyboard as it slides into view. This is due to our repositioning of content, which happens as soon as we receive the observer event. If we're going to change content like this, the lower boundary should adjust after the keyboard is fully displayed, or better yet, animate at the same rate as the keyboard. Blocking on bug 831982 for now, although we could probably kick this out as a stand alone defect.
Assignee | ||
Updated•11 years ago
|
Whiteboard: p=10
Comment 1•11 years ago
|
||
New story required.
Flags: needinfo?(asa)
Priority: -- → P2
QA Contact: jbecerra
Summary: Repositioning content for skb display should match keyboard animation → Story - Repositioning content for skb display should match keyboard animation
Whiteboard: p=10 → feature=story c=Content_features u=metro_firefox_user p=10
Updated•11 years ago
|
Blocks: metrov1backlog
Assignee | ||
Comment 2•11 years ago
|
||
This should really just be a bug, not a story.
Assignee | ||
Updated•11 years ago
|
Summary: Story - Repositioning content for skb display should match keyboard animation → Story - Repositioning content for skb display
Assignee | ||
Updated•11 years ago
|
Component: Input → Metro Operations
Product: Firefox for Metro → Tracking
Version: Trunk → ---
Assignee | ||
Comment 3•11 years ago
|
||
Converted this over to a more general tracker related to content repositioning when the soft keyboard is displayed. There are probably other bugs floating out there that can block this.
Assignee | ||
Updated•11 years ago
|
Whiteboard: feature=story c=Content_features u=metro_firefox_user p=10 → feature=story c=Content_features u=metro_firefox_user p=tbd
Assignee | ||
Updated•11 years ago
|
Whiteboard: feature=story c=Content_features u=metro_firefox_user p=tbd → [forms] feature=story c=Content_features u=metro_firefox_user p=tbd
Updated•11 years ago
|
No longer blocks: 831565, metrov1backlog
Summary: Story - Repositioning content for skb display → Work - Repositioning content for skb display
Whiteboard: [forms] feature=story c=Content_features u=metro_firefox_user p=tbd → [forms] feature=work
Assignee | ||
Comment 4•11 years ago
|
||
I have a wip in the bug associated with that and am finding our current content positioning is interfering with the soft keyboard. So this should be addressed first.
Blocks: 833305
Assignee | ||
Updated•11 years ago
|
Summary: Work - Repositioning content for skb display → Story - Repositioning content for skb display
Assignee | ||
Updated•11 years ago
|
Whiteboard: [forms] feature=work → [forms] feature=story
Assignee | ||
Comment 5•11 years ago
|
||
The work bugs are bug 854182 and bug 855235. There will be a few more most likely.
Comment 6•11 years ago
|
||
Hey Jim, do you want this bug as a story with its own point estimation or just a work item with bug 854182 and bug 855235 as dependencies? If you want it as a story, please provide a point estimation.
Flags: needinfo?(jmathies)
Assignee | ||
Updated•11 years ago
|
Whiteboard: [forms] feature=story → [forms] feature=story p=10
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(jmathies)
Comment 7•11 years ago
|
||
Thanks Jim. Added as a story. Using points from scope change contingency.
Flags: needinfo?(asa)
Whiteboard: [forms] feature=story p=10 → [forms] feature=story c=Content_features u=metro_firefox_user p=10
Assignee | ||
Updated•11 years ago
|
Whiteboard: [forms] feature=story c=Content_features u=metro_firefox_user p=10 → [forms] feature=story c=Content_features u=metro_firefox_user p=15
Updated•11 years ago
|
Blocks: metrov1it5
Updated•11 years ago
|
Assignee: nobody → jmathies
Status: NEW → ASSIGNED
Assignee | ||
Updated•11 years ago
|
Alias: skb
Assignee | ||
Comment 9•11 years ago
|
||
Comment 10•11 years ago
|
||
Flags: needinfo?(asa)
Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(jbecerra)
Resolution: --- → FIXED
Comment 11•11 years ago
|
||
Tested on 2013-04-15 using latest nightly built from http://hg.mozilla.org/mozilla-central/rev/261d6997d1d1 - Tested the basic user story from comment #10 and that works fine now. - Opened a defect bug 861945 for the inconsistency that happens when toggling between the Start view in Windows 8 and the Nightly tile.
Status: RESOLVED → VERIFIED
Flags: needinfo?(jbecerra)
Whiteboard: [forms] feature=story c=Content_features u=metro_firefox_user p=15 → [forms] feature=story c=Content_features u=metro_firefox_user p=15 status=verified
Comment 12•11 years ago
|
||
Went through the following "Story" for iteration #9 testing without any issues. Used the following build: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-07-09-03-02-04-mozilla-central/ - Went through the story that has been attached in comment 10 without any issues - Select "Comment", "URL", "Whiteboard", "Keywords" under "Detailed Bug Information" and the OSK slides in moving the text box into center view - Went through the all the test cases in "Filled" view without any issues Possible issues found: - Found another possible issue that is related to Bug 861945 that Juan posted, see comment Bug 861945 Comment 8 - When selecting "blank" text boxes (comment, URL, Whiteboard, Keywords), everything behaves the same other then the monocles appearing with the cursor. Currently, only the cursor is displayed without any monocles. Asa, is an issue? The story describes that once the text box is selected, the cursor + monocle should appear
Flags: needinfo?(asa)
Comment 13•11 years ago
|
||
I have been testing this for iteration #10 and I still see some inconsistencies with the skb. This morning when I tried going through the story in comment #10 the skb did not come up at all, even if I toggled between using touch and touchpad to focus on the form fields. I had to disconnect the keyboard from the Surface Pro before I was able to see a skb. Later, the page would not automatically scroll as the skb came up, but this only happened once. Unfortunately I haven't found a way to reproduce these two issues yet.
Assignee | ||
Comment 14•11 years ago
|
||
(In reply to juan becerra [:juanb] from comment #13) > I have been testing this for iteration #10 and I still see some > inconsistencies with the skb. This morning when I tried going through the > story in comment #10 the skb did not come up at all, even if I toggled > between using touch and touchpad to focus on the form fields. I had to > disconnect the keyboard from the Surface Pro before I was able to see a skb. From my experience with the touch cover on a surface pro, ms never brings up the soft keyboard if a physical keyboard is attached to the device. You can work around this by using a bluetooth keyboard. I'm using the samsung one that came with my series 7 to test at my desk.
Comment 15•11 years ago
|
||
User Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:26.0) Gecko/20100101 Firefox/26.0 Build ID: 20130812030209 Built from http://hg.mozilla.org/mozilla-central/rev/87c1796bc46c WFM Tested on windows 8 using latest nightly for iteration-11. Followed steps provided in user story and got expected result.
Comment 16•11 years ago
|
||
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 Build ID: 20130825030201 Built from http://hg.mozilla.org/mozilla-central/rev/01576441bdc6 WFM Tested on windows 8 using latest nightly for iteration-12. Followed steps provided in user story from comment10 and got expected result.
Updated•11 years ago
|
Flags: needinfo?(asa)
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
Updated•5 years ago
|
Product: Tracking → Tracking Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•