Closed Bug 861945 Opened 11 years ago Closed 11 years ago

Work - skb content offset lost after deactivating the browser window

Categories

(Firefox for Metro Graveyard :: Input, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jbecerra, Unassigned)

References

Details

(Whiteboard: [forms] feature=work)

Attachments

(1 file)

Tested on 2013-04-15 on latest nightly built from http://hg.mozilla.org/mozilla-central/rev/261d6997d1d1

While verifying bug 850413 I noticed that if you when to the the Start page and back while having the software keyboard, the positioning of it relative to the content is sometimes inconsistent.

Steps:
1. In Firefox for Metro go to https://bugzilla.mozilla.org/query.cgi?format=advanced
2. Expand the Custom Search field at the bottom
3. Tap on the text field
- At this point you should see the software keyboard come up.
4. Click on the Start key which should show you all the app tiles
5. Tap on the Nightly tile to come back to your Firefox for Metro

Expected: The Nightly should be on the same page with the software keyboard showing and the content should show the text field focused above the soft keyboard.

Actual: The software keyboard is displayed on top of the text field.

Once you get into this situation the positioning of the software keyboard relative to the content may vary. Sometimes it's displayed correctly, sometimes it overlaps the focused content.
Blocks: skb
Summary: defect - inconsistent position of skb display → Defect - inconsistent position of skb display
Whiteboard: [forms] feature=defect c=Content_features u=metro_firefox_user p=0
Summary: Defect - inconsistent position of skb display → Defect - skb content offset lost after deactivating the browser window
Hi Jim.  Asa is nominating this defect for iteration #6.  Can you provide a point estimate.
Flags: needinfo?(jmathies)
p=3 maybe? not sure about this one.
Flags: needinfo?(jmathies)
OS: Windows 8 → Windows 8 Metro
Component: General → Input
Thanks Jim.  Give it some thought for today's meeting.
Whiteboard: [forms] feature=defect c=Content_features u=metro_firefox_user p=0 → [forms] feature=defect c=Content_features u=metro_firefox_user p=3
Blocks: metrov1it6
No longer blocks: metrov1defect&change
Point Estimate = 3
Blocks: metrov1defect&change
No longer blocks: metrov1it6
Whiteboard: [forms] feature=defect c=Content_features u=metro_firefox_user p=3 → [forms] feature=defect c=Content_features u=metro_firefox_user p=0
I did some experimenting around on this. We can improve keyboard invocation by firing a uia event when the window activates. This tells windows to check for focused elements which it should find if a text input has it.

We still have an unknown display problem with the skb though, which I ran into while testing this. Will file a follow up on it that blocks this bug.
Depends on: 863676
Blocks: 855297
Hey Rodrigo, do you want to take this Defect (861945) as well since it blocks the story you have selected (855297)?
Flags: needinfo?(rsilveira)
Hey Rodrigo, ignore my last message.  Changing Bug 861945 to a work item since the blocked story is still open.
No longer blocks: metrov1defect&change
Flags: needinfo?(rsilveira)
Summary: Defect - skb content offset lost after deactivating the browser window → Work - skb content offset lost after deactivating the browser window
Whiteboard: [forms] feature=defect c=Content_features u=metro_firefox_user p=0 → [forms] feature=work
Ran into a similar issue when going through Bug 850413 for iteration #9 testing. Rather then going through the "Start" key route, I moved the mouse to the left corner of the screen while the OSK was displayed and switched over to the desktop. Once I returned to Firefox Metro, I had a white space instead of the OSK that quickly disappeared.

- Attached a screenshot to illustrate the issue

Steps to reproduce:

1) Follow the steps in comment 0 until you have the OSK displayed
2) Select the "Desktop" by moving your mouse to the top left corner and selecting the desktop
3) Go back to "Metro" mode and select "Nightly"
No longer depends on: 863676
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: