1359795 - Outlook Web Access move to folder search bar only allows one letter each time

Status: RESOLVED WORKSFORME

(Core :: DOM: Events, defect, P1)

Description

[jaime.bosque]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170417065206

Steps to reproduce:

When using Outlook Web Access interface the tool to categorize an email by using either the shortcut key (v) or click in the "Move to"  the search bar only allows typing one letter making it difficult to search for the actual folder if not listed from the suggestions show.
 


Actual results:

Everytime a letter is input, the focus on the search bar is lost, and it is required to click again on the search bar to introduce the second letter and so on.
Ej:
-> Click on Move To
-> Typed 'a'
-> Focus lost
-> Clik on Move To search bar
-> Typed 'b' (to create 'ab')



Expected results:

Search box should not lost the focus allowing the user to input several letters in order to categorize the email.

Comment 1

[Mike Taylor [:miketaylr]]

This still reproduces.

Comment 2

[Mike Taylor [:miketaylr]]

Attachment: owa.gif

In this gif, I'm trying to type "ab" to match a folder, but I lose focus after typing "a".

Note that typing "wwwww" succeeds, presumably because there's no fuzzy/meaningful match?

Comment 3

[Mike Taylor [:miketaylr]]

Tom, can you take a look please?

Comment 4

[Thomas Wisniewski [:twisniewski]]

Attachment: test.html

This is happening because the text input is losing its focus whenever the app decides to highlight one of the autocomplete entries under the input, either as-you-type, or when you mouseover over the entries, in the script https://r4.res.office365.com/owa/prem/16.2433.7.2583767/scripts/boot.owaframe.0.mouse.init.js

Ultimately this function is called in both cases, which highlights the desired autocomplete entry in blue by focusing its button element:

>  R: function () {
>    if (this.z.getAttribute('disabled')) return !1;
>    if (!this.bp())
>      try {
>        this.z.focus();
>        return !0
>      } catch (n) {
>        return !1
>      }
>    return !1
>  },

This causes the input to blur, at which point this function should re-focus it:

>  l: function () {
>    this.k || this.bs(this.b.length);
>    this.z.focus()
>  },

However, this does not work in Firefox. A focus event is not fired for the text input, just for the button. In Chrome however, the reverse happens: no event is fired on the button, just one on the text input.

I've attached a minimal (automated) test-case which shows this difference in behavior.

Comment 5

[Mike Taylor [:miketaylr]]

Andrew, do you know who would be able to best comment on focus/blur/input stuff?

Comment 6

[Andrew Overholt [:overholt]]

I tried a quick search in bugzilla and it looks like there are a number of previously-filed bugs about similar (or the same?) issues. Olli can probably provide some guidance on duping or knowing if there's spec divergence here.

Comment 7

[Firefox Bug Husbandry Bot]

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Comment 8

[Karl Dubost💡 :karlcow]

moving elsewhere as the diagnosis was done.

Comment 9

[Olli Pettay [:smaug][[e-mail]]]

This was a website issue.

Comment 10

[Hsin-Yi Tsai (she/her) [:hsinyi]]

This isn't reproducible to me with nightly 96.
Karl, can you confirm? If this is no longer an issue on the OWA, I suggest we lower the priority.

Comment 11

[Karl Dubost💡 :karlcow]

This is indeed working for me too.