chrome loses focus with java script interaction

[Bob Aloisi]

We have a page that builds an input field using JS. The user clicks buttons and the input field builds. At the end of each interaction we call setSelectionRange to position the cursor at a particular place in the input string. Thus the cursor is positioned for direct user input or to click another button to continue building. Prior to today, this worked fine in CHROME. As of today, the cursor is not longer positioned in the input (the field has lost focus) and there seems to be no programmatic way to re-obtain focus.

We have tested this in Firefox and Edge and it works fine. It just does not work in CHROME as of the last update

We have now moved to Firefox until this Chrome issue is resolved

[PhistucK]

This group discusses the Developer Tools feature of Google Chrome and not general web development issues.

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

Note that in order to fix this, the issue must be reproduced first, so you should prepare a URL that reproduces the issue and mention it in the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/a3d1e3f1-80ab-4d25-95ec-f5d1ddf721a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Larry LACa]

Phistuck: 

Bob posted to the Chrome Help Forum here 8/8, and Rochelle (Community Specialist) redirected him here.  Can you let Rochelle know that Chromium-Discuss is the better general choice?

Can you add Chromium-Discuss to your general redirect recommendation?

 

[PhistucK]

You are welcome to tell her (I am not a Googler, too). :)

Regarding suggesting chromium-discuss here - no, because, if anything, I think they should be posted first to stackoverflow.com and if it is still determined to be a Chrome bug, just file a bug at crbug.com and it will be triaged like the rest of the bugs. chromium-discuss is not a great place for reporting bugs and in most cases, they will be redirected from there to crbug.com.

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/29bf33f7-e46a-4596-95ce-1fef06ce6876%40googlegroups.com.