Tested the issue using #63.0.3208.0 on Android 5.1.1 Micro max, 7.1.0, Pixel XL. Able to login, but couldn't find any advanced search icon or option on the page to reproduce the issue.

@bahassinea: Could you please let us know where can we find the advanced search icon or option in that page by providing clear steps or screenshot? that would help us in further triaging of the issue.

Thanks!!

At the url i provided you you'll see a magnify icon (to make search)
Then try to edit the search profile called "rrrrrr" ( pencil icon).
Here is the search form.

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce the issue using #63.0.3208.0 on Android 5.1.1 Micro max, 7.1.0, Pixel XL. Observed the page is not responding on clicking text box's. 

This seems to be a Non-Regression issue as same behavior is seen since M59. Hence marking it as untriaged to get more input's from dev.

Thanks!! 

Please also test with 58 and try to bisect. We switched compilers in 59 and I want to make sure the switch isn't the culprit.

ligimole@ could you please facilitate a bisect? Thank you!

Sandeep, can you try in older version of chrome (58)= comment #7 and bisect if possible.

Below is the bisect info
=======================

Chrome Good Build -- 53.0.2774.0
Chrome Bad Build  -- 53.0.2779.0

https://chromium.googlesource.com/chromium/src/+log/53.0.2774.0..53.0.2779.0?pretty=fuller&n=10000

Results from pre revision bisect --
You are looking for a change made after 401460(GOOD), but before 401479(BAD).

From the above revision range suspecting the following --
https://chromium.googlesource.com/chromium/src/+/984ead6c20ef098f8af6b4da25600e01bd3303ef

@eroman -- Could you please look into the issue, kindly re-assign if this is not related to your changes.

Note:
1. Issue is seen in 7.1.2 Pixel XL Build/N2G48E, 6.0.1: SM-J710F Build/MMB29K, Pixel Build/OPR1 170623.027 as well
2. Issue is seen in M63 as well.

Thank You.

I checked and my changes in that regression range are not the culprit.

Unable to find the exact culprit from above CL. Hence Changing the status to Untriaged to get addressed from dev team.

Thanks!!

Please try the bisect again.

Just to update.

Retried the bisect, got same good and bad build range in Manual bisect and got same CL using pre revision bisect.

Manual CL:
https://chromium.googlesource.com/chromium/src/+log/53.0.2774.0..53.0.2779.0?pretty=fuller&n=10000

Results from pre revision bisect --
You are looking for a change made after 401460(GOOD), but before 401479(BAD).

Unable to find the suspect from the above CL

Thanks!!

I believe this is caused by https://chromium.googlesource.com/chromium/src/+/887e8fba784c801afbda06799a99284421408ff1

The site is swallowing the touchstart and preventDefaulting it but then dispatching a mouse down against the select to open it. But since the mouse down is an untrusted event it doesn't open the select. It seems to be doing this for fastclick.

Really the site should avoid preventDefaulting the touchstart.

bahassinea@ are you the site author?

Not P1 since it is from M53 and site specific.

No, i'm not the site author.

They have specific code.. it is minimized so it is hard to understand.

But they are checking that the tag element is select/option and then prevent defaulting it.
        /^(select|option)$/i.test(e.target.tagName) && e.preventDefault()),

Likewise they dispatch a mousedown at selects to open them. This doesn't work since Chrome 53.
        var t = !1;
        "SELECT" == e.tagName ? (n("mousedown", e, 0, 0),
        e.focus && e.focus(),
        t = !0) : m() === e ? t = !0 : /^(input|textarea)$/i.test(e.tagName) || e.isContentEditable ? (t = !0,
        e.focus && e.focus(),
        e.value = e.value,

The NextAction date has arrived: 2017-10-17