Marking the above issue as RB-Stable as this is a recent regression.

Thank you!

I don't think my patch causes this. We display the virtual keyboard here https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/renderer_host/render_view_host_impl.cc&q=DisplayVirtualK&sq=package:chromium&l=1303

This code runs in the browser. From what I can see it looks like when you touch the down or up arrow in the Find box in the dev tools inspector, blink is telling us that the node is editable, which is not correct. Please assign this to someone from the dev tools team.

@pfeldman: Hey, would you mind helping us in assigning it to correct owner as per comment#2 & from Narrow bisect in the original bug ?

I really appreciate your help.

Thank you!

Moving this nonessential bug to the next milestone.

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

====================================

Good Build:

52.0.2706.0    Base Position: 386523


Bad Build:

52.0.2707.0    Base Position: 386876

=====================================

Able to repro this issue on Windows 10 [Pro] for the Google Chrome Canary Version - 53.0.2760.0

This is a regression issue broken in M52, below mentioned is the bisect info:

CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/8e4a0b36ac3989db1afb69dff442fdc85af047da..44a0b274c777c0a6aee6f5ba722c435e71d54273?pretty=fuller&n=100

MANUAL CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/52.0.2706.0..52.0.2707.0?pretty=fuller&n=10000

Suspecting Below:

=======================================================

Commit:	e16154fa1a98b487a9e04feaad87fd31a3ae3fa4	

Review URL: https://codereview.chromium.org/1869853002

-------------------------------------------------------

Commit:	25c52c3f3c407fd9f5678c0079c877ccef34c090		

Review URL: https://codereview.chromium.org/1868363002

=======================================================

@alexmos/danakj: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner.

Thank you.

Sorry for missing this earlier.  I don't think my r386833 caused this - it only moves tests around and has no effect on browser behavior.  Reassigning to danakj@ to take a look at the second suspect.

My patch is a rename of "scoped_ptr" to "std::unique_ptr", sorry but not applicable.

=> sadrul do you know who owns virtual keyboard things?

I think this has more to do with issue 479301 (or something similar to that) than with the virtual keyboard.

I don't really know who does text-input in blink land these days. Perhaps tdresser@ knows?

Over to dtapuska@.

This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone.

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

Note: Above issue is reproducible on latest canary version: 55.0.2878.0