Closed
Bug 959414
Opened 12 years ago
Closed 11 years ago
[B2G][Contacts] Cancelling out of editing or Updating a contact after importing displays broken UI
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(blocking-b2g:1.3+, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 fixed)
People
(Reporter: tnguyen, Assigned: crdlc)
References
Details
(Keywords: regression)
Attachments
(5 files)
Description:
Cancelling out of editing or Updating a contact information promptly after importing a contact will have device display broken UI.
Repro Steps:
1) Updated Buri to BuildID: 20140113004002
2) Navigate to Contacts App
3) Tap on the Gear icon to open Contact Settings
4) Import a contacts from Gmail or Outlook
5) Return to the contacts list
6) Tap on an contact just added
7) Edit contact details by tapping on top right icon
8) Tap on any text field area, then tap on a few random text keys
9) Tap the "X" to cancel or "Update"
Actual:
Contact App has broken UI when the user tries to edit a contact promptly after importing a contact
Expected:
There are no UI issues in the contacts app
Environmental Variables:
Device: Buri v1.3 mozRIL
BuildID: 20140113004002
Gaia: b3fc4f712562ee92b0ed0bd17abc61be9a36a8da
Gecko: 5bb1837de7c0
Version: 28.0a2
Firmware Version: v1.2-device.cfg
Notes:
Repro frequency: 5/5 100%
See attached: screenshot, logcat
Reporter | ||
Comment 1•12 years ago
|
||
Reporter | ||
Comment 2•12 years ago
|
||
This issue does not reproduce on the latest Buri 1.2 build.
Environmental Variables:
Device: Buri v1.2 comRIL
BuildID: 20140113004002
Gaia: 539a25e1887b902b8b25038c547048e691bd97f6
Gecko: e672faf1e6a1
Version: 26.0
RIL Version: 01.02.00.019.102
Firmware Version: v1.2-device.cfg
This issue does occur on the latest Buri Master M-C build but seems to be a different issue. Typing just a single character into any of the text fields results in the broken UI displaying. I think the two issues may be related and can write a separate issue if requested.
Environmental Variables:
Device: Buri Master M-C
BuildID: 20140113040202
Gaia: fd3b9a97cb3c41cfa56be387b46a51db136b4422
Gecko: 12d3ba62a599
Version: 29.0a1
Firmware Version: v1.2-device.cfg
Updated•12 years ago
|
blocking-b2g: --- → 1.3?
Keywords: regression,
regressionwindow-wanted
Updated•12 years ago
|
QA Contact: jzimbrick
Comment 3•12 years ago
|
||
Regression Window:
Last Working Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140111004005
Gaia: 1f029aa4c924d6c59fd7e8c6d9786a7370755d49
Gecko: 89c68fcb1448
Version: 28.0a2
Base Image: V1.2-device.cfg
First Broken Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140112004002
Gaia: 1f029aa4c924d6c59fd7e8c6d9786a7370755d49
Gecko: c42fd6b6d1fc
Version: 28.0a2
Base Image: V1.2-device.cfg
Keywords: regressionwindow-wanted
Updated•12 years ago
|
blocking-b2g: 1.3? → 1.3+
Comment 5•12 years ago
|
||
I'm seeing this javascript error when trying it against current master:
E/GeckoConsole( 787): [JavaScript Error: "TypeError: keyboard.sendKey(...) is undefined" {file: "app://keyboard.gaiamobile.org/js/imes/latin/latin.js" line: 406}]
Jan is this familiar to you?
Flags: needinfo?(janjongboom)
Comment 6•12 years ago
|
||
Happens when APZC is enabled. See bug 959198...
Flags: needinfo?(janjongboom)
Comment 7•12 years ago
|
||
Per comment 6, I've disabled APZC in the settings menu and I'm not able to reproduce that error.
Asking for QA to verify if it's not happening with APZ.
Keywords: qawanted
Comment 8•12 years ago
|
||
When APZC is enabled, the issue reproduced. When APZC is disabled, the issue does not reproduce.
Gaia a81ccdc53e45a6adeaae423e104e91bcc1e12b0e
SourceStamp 2c033140eff4
BuildID 20140117004005
Version 28.0a2
Keywords: qawanted
Updated•12 years ago
|
Component: Gaia::Contacts → Panning and Zooming
Product: Firefox OS → Core
Version: unspecified → 28 Branch
Comment 10•12 years ago
|
||
Waiting for bug 959198 to be resolved first.
Flags: needinfo?(bugmail.mozilla)
Comment 11•12 years ago
|
||
Milan, Vivien, this blocks 1.3 CS.
Flags: needinfo?(milan)
Flags: needinfo?(21)
Comment 12•12 years ago
|
||
(In reply to David Scravaglieri [:scravag] from comment #11)
> Milan, Vivien, this blocks 1.3 CS.
I'm going to land the patch for APZ to be enable everywhere today.
Flags: needinfo?(21)
Comment 13•12 years ago
|
||
(In reply to David Scravaglieri [:scravag] from comment #11)
> Milan, Vivien, this blocks 1.3 CS.
Yes, see Comment 10.
Flags: needinfo?(milan)
Updated•12 years ago
|
Reporter | ||
Comment 15•11 years ago
|
||
After bug 959198 has been resolved as fixed, this issue still reproduces so I am reopening this bug.
Environmental Variables
Device: Buri v 1.3.0 Mozilla RIL
Build ID: 20140210004002
Gecko: https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/9c9382f433c0
Gaia: 5c8416fb1ea4a27f172ee6386ab3c19135448506
Platform Version: 28.0
Firmware Version: v1.2-device.cfg
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 17•11 years ago
|
||
So I can reproduce an issue where I see the thing in the screenshot in comment 0, but it's only transient (stays for less than 1 second) and then repaints properly. Is that the entirety of the issue? Or are you seeing the "broken UI" persist?
Flags: needinfo?(tnguyen)
Comment 18•11 years ago
|
||
FWIW it looks like when the keyboard is dismissed it shows some stuff that is sitting underneath. Sometimes it is the error page you see in the screenshot and sometimes it is just blank white. I see this both with and without APZ so I'm thinking this might be a contacts app bug. But I can look into it more and see what I find.
Comment 19•11 years ago
|
||
The error page from the screenshot comes from the <iframe id="fb-extensions"> and temporarily becomes visible when the keyboard is hidden. I presume this is because the content that's supposed to be showing doesn't resize fast enough. If I set this iframe to display:none in the app manager then I see something else instead of that error page (I guess whatever is underneath the iframe).
Reporter | ||
Comment 20•11 years ago
|
||
Hi Kats, the issue is that the error as seen in the screenshot only appears briefly and then repaints properly.
Flags: needinfo?(tnguyen)
Comment 21•11 years ago
|
||
Ok, thanks. And good job on grabbing a screenshot of that then! :) I would have found it pretty hard to time that just right.
For the record I don't think is a severe enough glitch to warrant status of "CS blocker" but I don't really know what criteria Mandyam is using for that so you guys can figure that out.
I'm going to try to figure out why the stuff on top (the contact editor and display sections) seem to be resizing slower than the iframes under it, which seems to be the underlying problem that causes the glitch.
Comment 22•11 years ago
|
||
Ok, so I think what's happening is this:
When you're in the "edit contacts" screen with the keyboard displayed, the window size doesn't include the keyboard area. So all the content is sized to fit in the top half of the screen. The <iframe id="fb-extensions"> has style properties "position:fixed; top: 100%" which means that it is located just below the content area (i.e. behind the keyboard). When the keyboard is dismissed but before the reflow happens, we paint the same content (with the smaller window size) but without the keyboard. Therefore the iframe hiding under the keyboard becomes visible. As soon as finish processing the resize and reflow, things go back to normal.
This seems like a problem with how the contacts app chooses to "hide" things offscreen (i.e. using "position:fixed;top:100%" instead of say "display:none" or "visibility:hidden" or even "position:fixed;top:-100%"). Since the underlying problem exists even without APZ I'm moving this bug to the contacts app. Somebody who knows the contacts code should look into this and find some other way to hide elements that they don't want to be visible.
Assignee: bugmail.mozilla → nobody
Component: Panning and Zooming → Gaia::Contacts
Product: Core → Firefox OS
Version: 28 Branch → unspecified
Comment 23•11 years ago
|
||
Also note that there's a bunch of stuff stacked in the same spot as that iframe, so just setting display:none on the iframe alone doesn't fix the problem - I end up seeing whatever else is stacked under there.
Comment 24•11 years ago
|
||
Jose or Francisco, any chance that you can tweak how the iframe goes offscreen here in order to solve the issue ?
For example once the animation of the iframe is done, you can likely set the iframe visibility to hidden.
Flags: needinfo?(jmcf)
Flags: needinfo?(francisco.jordano)
Comment 25•11 years ago
|
||
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #24)
> Jose or Francisco, any chance that you can tweak how the iframe goes
> offscreen here in order to solve the issue ?
>
> For example once the animation of the iframe is done, you can likely set the
> iframe visibility to hidden.
Same for whatever frame is at this place.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → crdlc
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 27•11 years ago
|
||
Attachment #8376133 -
Flags: review?(jmcf)
Attachment #8376133 -
Flags: review?(francisco.jordano)
Assignee | ||
Comment 28•11 years ago
|
||
Comment on attachment 8376133 [details]
Patch v1 for 1.3
Jose is peer, Jordano's review is not needed, just one is enough
Attachment #8376133 -
Flags: review?(francisco.jordano)
Comment 29•11 years ago
|
||
Comment on attachment 8376133 [details]
Patch v1 for 1.3
r+ for the patch that hides all the iframes and status content in a way that it will not be visible if there is a window resize.
Please note that this patch only solves the problem at contacts level but the issue (without seeing contacts hidden content) is still reproducible (see attached screenshot).
Attachment #8376133 -
Flags: review?(jmcf) → review+
Flags: needinfo?(francisco.jordano)
Updated•11 years ago
|
Assignee: crdlc → nobody
Comment 30•11 years ago
|
||
Comment on attachment 8376133 [details]
Patch v1 for 1.3
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #):
[User impact] if declined: high, spureous content will be seen. low quality perceived
[Testing completed]: smoke test done
[Risk to taking this patch] (and alternatives if risky): low risk
[String changes made]:
Attachment #8376133 -
Flags: approval-gaia-v1.3?(fabrice)
Comment 31•11 years ago
|
||
while closing the edit screen if the keyboard was open the transition plays as it the window were smaller.
Comment 32•11 years ago
|
||
Vivien,
The contacts issues regarging hiding auxiliary content have been solved. However, there is still the issue described in comment #31 and its corresponding attachment.
thanks!
Flags: needinfo?(21)
Updated•11 years ago
|
Target Milestone: --- → 1.4 S1 (14feb)
Updated•11 years ago
|
Target Milestone: 1.4 S1 (14feb) → ---
Assignee | ||
Comment 33•11 years ago
|
||
It the same code but for master
Attachment #8376208 -
Flags: review?(jmcf)
Assignee | ||
Updated•11 years ago
|
Attachment #8376133 -
Attachment description: Patch v1 → Patch v1 for 1.3
Comment 34•11 years ago
|
||
Comment on attachment 8376208 [details]
Patch v1 master
thanks, Cristian. Please land this on master once you get a green Travis
Attachment #8376208 -
Flags: review?(jmcf) → review+
Assignee | ||
Comment 35•11 years ago
|
||
ok, will do
Comment 36•11 years ago
|
||
(In reply to Jose M. Cantera from comment #31)
> Created attachment 8376203 [details]
> issue after applying contacts patch
>
> while closing the edit screen if the keyboard was open the transition plays
> as it the window were smaller.
The screen is actually smaller. I have a plan to help here in bug 970093 but it will require some time.
I think we need to ask QA to reevaluate if the bug is still a blocker with the patch from Christian.
Flags: needinfo?(21)
Assignee | ||
Comment 37•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 38•11 years ago
|
||
Can someone from QA verify this before we decide on approval? thanks!
Flags: needinfo?(jsmith)
Keywords: qawanted
Comment 39•11 years ago
|
||
(In reply to Fabrice Desré [:fabrice] from comment #38)
> Can someone from QA verify this before we decide on approval? thanks!
Sure - I'll look at this on Tuesday.
Comment 40•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #39)
> (In reply to Fabrice Desré [:fabrice] from comment #38)
> > Can someone from QA verify this before we decide on approval? thanks!
>
> Sure - I'll look at this on Tuesday.
Going to put needinfo on the reporter to retest this on master with the patch.
Flags: needinfo?(jsmith) → needinfo?(tnguyen)
Updated•11 years ago
|
Comment 41•11 years ago
|
||
This issue still occurs on latest 1.3
Reproduces with the original STR in comment 0, as well as when tapping on textbox while editing a contact, then deselecting same textbox. Both methods reveal same broken UI with shown in Attachment 8359514 [details]. Clearing needinfo after discussing with tnguyen. This appears to be same issue, should this bug be reopened, or should a new bug be filed?
Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140218004003
Gaia: df60e9b49207d64da5647ab15760c122adabfba4
Gecko: b5afe0b10e93
Version: 28.0
Firmware Version: v1.2-device.cfg
Flags: needinfo?(tnguyen)
Keywords: verifyme
Comment 42•11 years ago
|
||
(In reply to Brogan Zumwalt from comment #41)
> This issue still occurs on latest 1.3
>
> Reproduces with the original STR in comment 0, as well as when tapping on
> textbox while editing a contact, then deselecting same textbox. Both methods
> reveal same broken UI with shown in Attachment 8359514 [details]. Clearing
> needinfo after discussing with tnguyen. This appears to be same issue,
> should this bug be reopened, or should a new bug be filed?
>
> Environmental Variables:
> Device: Buri v1.3 Mozilla RIL
> BuildID: 20140218004003
> Gaia: df60e9b49207d64da5647ab15760c122adabfba4
> Gecko: b5afe0b10e93
> Version: 28.0
> Firmware Version: v1.2-device.cfg
We should backout & reopen the bug.
Cristian - Can you backout & reopen?
Flags: needinfo?(crdlc)
Comment 43•11 years ago
|
||
Comment on attachment 8376133 [details]
Patch v1 for 1.3
Marking a- as the patch here fails to solve the problem in the bug.
Attachment #8376133 -
Flags: approval-gaia-v1.3?(fabrice) → approval-gaia-v1.3-
Assignee | ||
Comment 44•11 years ago
|
||
But if the code is not landed on 1.3 yet. According to my managers we need a approval‑gaia‑v1.3+ to land something in v1.3. For this reason I didn't push the fix :)
Flags: needinfo?(crdlc)
Assignee | ||
Updated•11 years ago
|
status-b2g-v1.3:
--- → affected
status-b2g-v1.4:
--- → fixed
Comment 45•11 years ago
|
||
Oh wait. I understand now. The testing done above was wrong - it was done on 1.3. Sorry about that. I'll reflag again for this to be tested on master.
Flags: needinfo?(bzumwalt)
Comment 46•11 years ago
|
||
Comment on attachment 8376133 [details]
Patch v1 for 1.3
Resetting approval flag since the testing done here was done incorrectly.
Attachment #8376133 -
Flags: approval-gaia-v1.3- → approval-gaia-v1.3?
Comment 47•11 years ago
|
||
Issue described in comment 31 still occurs in latest 1.4 master following STR from comment 0
Result: Animated transition when closing edit contact screen behaves as though window is smaller than it actually is.
Video showing issue: http://www.youtube.com/watch?v=-RJkwq-RcAY
Environmental Variables:
Device: Buri v1.4 Master Mozilla RIL
BuildID: 20140219040204
Gaia: ac06cfbd2baf6494ffbb668cc599e3892cd5e17b
Gecko: bf0e76f2a7d4
Version: 30.0a1
Firmware Version: v1.2-device.cfg
Flags: needinfo?(bzumwalt)
Keywords: verifyme
Comment 49•11 years ago
|
||
Should this be re-opened?
Comment 50•11 years ago
|
||
The issue in comment 31 is expected, as Vivien said in comment 36. There's no easy way to fix that without implementing a floating keyboard.
If that's the only issue left then I think the fix can be considered verified and uplifted.
Comment 51•11 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #50)
> The issue in comment 31 is expected, as Vivien said in comment 36. There's
> no easy way to fix that without implementing a floating keyboard.
>
> If that's the only issue left then I think the fix can be considered
> verified and uplifted.
Okay - sounds okay to me then.
Assignee | ||
Comment 52•11 years ago
|
||
Sorry guys, it is not been uplifted to v1.3 because we don't have the approval
Comment 53•11 years ago
|
||
Fabrice, could please help us with the approval here?. Thanks!
Flags: needinfo?(fabrice)
Updated•11 years ago
|
Attachment #8376133 -
Flags: approval-gaia-v1.3? → approval-gaia-v1.3+
Updated•11 years ago
|
Target Milestone: --- → 1.4 S2 (28feb)
Comment 55•11 years ago
|
||
Tested 02/24/2014 and working
1.3
Gecko cf974e3
Gaia 5084b83
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
status-b2g-v1.3T:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•