1301175 - Microsoft Outlook 365 OWA - Clicking on items don't trigger preview with touch events enabled

Status: RESOLVED DUPLICATE of bug 1294734

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Piotr Paczkowski]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20160907030427

Steps to reproduce:

Reference bug: http://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_other/outlook-owa-doesnt-react-on-clicking-on-emails/1a3483e4-6c3b-4608-bea5-f1448462c35e

* login to some OWA service with mail.
* Navigate to inbox
* click on any item in inbox 

This issue doesn't occur on release Firefox. 


Actual results:

* nothing


Expected results:

* clicked item should invoke preview on the side.

-----

I realize that this bug has very poor description, nevertheless please let me know how I can provide you additional information in order to confirm if this is actually Firefox problem, or problem in MS implementation.

Comment 1

[Loic]

Does it work with the release version FF48?

If it's broken in FF51 (according to your user agent), can you test with e10s disabled? (Options > General)

Is there a possibility to provide URL to test the issue? (even with limited rights like guest account)

Comment 2

[Piotr Paczkowski]

Hi @Loic: "Enable multi-process Nightly" is disabled, and grayed out. 
It might be problematic to give access to my account, but I can talk with IT if we can create a test account that has only access to an email inbox. I'm not promising that it will actually be possible. 

Can you give some advice how I can approach this problem? I can try to identify exact version of Firefox that brings this problem. Do you have an archived version of nightly builds?

Comment 3

[Loic]

As a good start, you can download the tool Mozregression to narrow down a regression range in FF50 or 51.
See http://mozilla.github.io/mozregression/ for details.

The tool downloads automatically nightly builds (by dichotomy) and for each build, make your test (visiting Outlook OWA) and enter if the build is good or bad.
At the end, copy here the final pushlog from repository mozilla-inbound.

If e10s is an issue when bisecting, you can start the run with the command --pref "browser.tabs.remote.autostart:false"

Comment 4

[Piotr Paczkowski]

@Loic it looks that it found a place where it started to happen, and fixed bug that comes with this version has is connected to mouse/touch input: 
Bug 1180706 - Enable touch event support on Windows Nightly. r=botond


First build where this issue exists: 
```
app_name: firefox
build_date: 2016-01-30 04:30:17.188000
build_file: C:\Users\piotr\.mozilla\mozregression\persist\1056404c052e--mozilla-inbound--firefox-47.0a1.en-US.win64.zip
build_type: inbound
build_url: https://queue.taskcluster.net/v1/task/KuNx4ClrRYufgYjel0rrag/runs/0/artifacts/public%2Fbuild%2Ffirefox-47.0a1.en-US.win64.zip
changeset: 1056404c052eea689459638d6cb57fd888318a35
pushlog_url: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=4891238709e17274db6ffa4880730b97ff6c24da&tochange=1056404c052eea689459638d6cb57fd888318a35
repo_name: mozilla-inbound
repo_url: https://hg.mozilla.org/integration/mozilla-inbound
task_id: KuNx4ClrRYufgYjel0rrag
```

I'm pretty impressed by simplicity of testing with Mozregression.

Connected diff https://bugzilla.mozilla.org/attachment.cgi?id=8713677&action=diff hints me to change value of `dom.w3c_touch_events.enabled` to 0, and it worked.

What is next in this case?

Comment 5

[Loic]

If you set dom.w3c_touch_events.enabled=0 in about:config (maybe eestart FF to apply), does Outlook works normally in FF51?

Comment 6

[Loic]

Ok, I didn't see your last sentence, so it's completely related to touch events.

Comment 7

[Loic]

botond, can you look at this bug, or request NI to someone aware of touch events issues.

Comment 8

[Piotr Paczkowski]

I confirm that this behavior is reflected in current Firefox 48. Hence my first assumption that this is something recent is wrong.

Comment 9

[Botond Ballo [:botond]]

I'll investigate in more detail on Monday, but it sounds like this may be a duplicate of bug 1294734, which is an evangelism issue.

Comment 10

[Kartikaya Gupta (email:[e-mail])]

This definitely seems like a dupe of bug 1294734. Presumably this doesn't work in Chrome either.

Comment 11

[Botond Ballo [:botond]]

I just tested the STR of bug 1294734 (and of this bug, which is basically the same) again today, and it looks like Outlook have fixed the issue on their side.

Piotr, are you still seeing this problem? The fix may have been as recent as within the last day.

Comment 12

[Piotr Paczkowski]

Hi Botond, 
I set `dom.w3c_touch_events.enabled=2` and after restart I visited OWA portal. 
Indeed I can see an updated version of OWA, and this issue doesn't exist anymore. 

So it looks that it was fixed there like you said. Thank you for following this topic.