Closed Bug 1186635 Opened 9 years ago Closed 7 years ago

[Aries][Contacts] Import Contacts from Outlook screen cannot be zoomed after device restart.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:+, b2g-master affected)

RESOLVED WONTFIX
tracking-b2g +
Tracking Status
b2g-master --- affected

People

(Reporter: NicholasN, Unassigned)

References

()

Details

(Whiteboard: [2.5-Daily-Testing][Spark])

Attachments

(2 files)

Attached file logcat_import.txt
Description:
In the Contacts app, the user taps the settings (cog) icon, and then goes to Import Contacts. They select Outlook, and are taken to login.live.com. If the user has not restarted the device after flashing/updating, they can pinch to zoom on this page. Additionally, if this page is accessed in the FTU it can also be zoomed. However, if they have restarted the device, the page in contacts cannot be zoomed. 


Repro Steps:
1) Update an Aries to 20150722124026
2) Once on the homescreen, restart the device.
3) Open the contacts app, and tap the settings icon.
4) Select import contacts, and then select Outlook.
5) Attempt to zoom on login.live.com


Actual:
Log-in page cannot be zoomed.


Expected:
Log-in page can be zoomed.


Notes:

Environmental Variables:
Device: Aries 2.5
Build ID: 20150722124026
Gaia: b57aef5b7f52c40f88ee4c069ff722404e8e8521
Gecko: 954706e7611c
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0


Repro frequency: 5/5
See attached: video clip, logcat
Note: The issue still reproduced after disabling hardware composer in developer settings.

Issue reproduces on older Aries builds, but not on Flame.

Aries 2.5 (RC4 build)

Actual Result:

Log-in page cannot be zoomed.

Environmental Variables:
Device: Aries 2.5
BuildID: 20150619225606
Gaia: 4c06ed88ddccaba8dc941e5006bd2a9e57306f07
Gecko: 7c1a6b1151a1539186b950a144387e2d7f378d1b
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 41.0a1 (2.5) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Flame 2.5

Actual Result:

Log-in page can be zoomed.

Environmental Variables:
Device: Flame 2.5
BuildID: 20150722010204
Gaia: 84c3bf622e211046d905803b34de5d331761f22d
Gecko: 8e5c888d0d89
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Whiteboard: [2.5-Daily-Testing][Spark]
NI on component owner for nomination decision.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(jlorenzo)
[Blocking Requested - why for this release]: Functional regression on the new reference device (compared to the old one).

The Outlook import page is just the Outlook website being rendered by Gecko. Moving the issue there.
blocking-b2g: --- → 2.5?
Component: Gaia::Contacts → Panning and Zooming
Flags: needinfo?(jlorenzo)
Product: Firefox OS → Core
This is a result of the customizer add-on screwing with the touch events.
Component: Panning and Zooming → Gaia::Customizer
Product: Core → Firefox OS
This is a log of various gecko-side log things as I start a pinch. The log shows that the child process is seeing (1) a touchstart with one touch point, but the wrong block id, (2) a touchstart with two touch points which is correct, and (3) a touchstart with two touch points but coordinates that seem way off.

The wrong block id is not really a problem since the APZ code is robust enough to handle that, but it's the result of the customizer addon holding on to the first touchstart event and then injecting that during the handling of the second touchstart. This results in the block id of the second touchstart getting applied to the first touchstart.

The real problem is (3) where the last touchstart sets a bad target APZ and prevents zooming. I don't know where this is coming from, but disabling the customizer add-on makes everything behave as expected.
Actually my interpretation in comment 5 might be slightly off. I think the real problem might be that the first two touchstart events are getting targetted to the wrong frame.
Removing nomination as its specific to Windows Live site and needs more investigation.
blocking-b2g: 2.5? → ---
tracking-b2g: --- → +
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: