Did this work before? Yes before v58 it work fine

Tried testing the issue on Win-7 and Win-10 using chrome latest stable #61.0.3163.79 and latest canary #63.0.3206.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened chrome browser and navigated to https://google.co.in
2. Using <input type="text" name="UserId" id="login_UserId" value="" size="20" autocomplete="off">, created a html file.
3. Opened the html file in the browser.
4. Observed an input text field with no cursor available. When clicked inside the field, a cursor appeared which allowed to type.

Note: Same behavior is observed in firefox and in chrome version M58 also.

Reporter@ - Could you please verify the screen cast and please let us know if anything missed from our side. If possible please provide a screen cast explaining the exact issue. This will help us in triaging the issue better.

Thanks...!!

Deleted: 761894.mp4 1.2 MB

	761894.mp4 1.2 MB View Download

Hi 

Try to open that page Non secure way. where user need to accept risk.
Due to privacy reason , i can't screent cast the issue.It may be reproduce.

Regards,
Chetan Kolhe

Deleted: 1.PNG 34.8 KB

	1.PNG 34.8 KB View Download

Deleted: 2 link.PNG 5.2 KB

	2 link.PNG 5.2 KB View Download

Thank you for providing more feedback. Adding requester "krajshree@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

Tested this issue on Windows 10 with chrome #60.0.3112.113

Observations:
1. Created a html page from provided coded in comment #0
2. Started python web server on windows machine.
3. Loaded test page with "http" and didn't observe any cursor in the input field.
4. Load test page with "https"  and observed an error "This site can’t be reached". Didn't see error like "Your Connection is not private"

Attaching the screen-cast for reference. 

chetankolhe72@ Could you please look into it and help us with html page for further triage.

Thank You...

 

Deleted: 761894.mp4 667 KB

	761894.mp4 667 KB View Download

Thank you for providing more feedback. Adding requester "kkaluri@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

Hi 

I have confirmed using other product where user need to accept the exception, this is the chrome issue.
Firstly,*** Didn't see error like "Your Connection is not private" *** it is not a error.

“Your connection is not private” or Net::ERR_CERT_DATE_INVALID error appears on screen due to the SSL error. SSL (secure sockets layer) is used by the Websites to keep all the information you enter on their pages private and secure. If you are getting the SSL error Net::ERR_CERT_DATE_INVALID in Google chrome browser, it means your Internet connection or your computer is preventing Chrome from loading the page securely and privately.

Above web application, you have not created using ssl.
Due to security reason, we can't share our data. I am trying to create dummy web application where ssl is there. Please make afford from your side also.

Regards ,
Chetan

@Reporter- Let us know if the dummy web application is ready for testing to check this issue from chrome-TE end.

Thanks!

Any further progress on this? If we don't have a reproduction URI we will have to close the issue as not reproducible.

The NextAction date has arrived: 2017-09-27

Hi, 

Currently this issue not reproducing on latest version.
Version 61.0.3163.100 (Official Build) (64-bit)

May be this issue get fix in this build with other bug.
I will check if the same issue get reproduce with other product or not.

Thanks & Regards,
Chetan Kolhe

Thank you for providing more feedback. Adding requester "brajkumar@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

Removing the Needs-Bisect label as per comment #13 and waiting for reporter to update the behavior of the issue.
Please feel free to add the same if required.

Thanks...!!

Closing as per comment #13.