Blocked autofocusing on a form control in a cross-origin subframe.
See original GitHub issueHi: I installed the release 2.1698-vsc1.41.1, and I use this command and set a password to start it:
code-server --host 0.0.0.0 --port 8082
this is ok to run. But when i put it in iframe, when send the password will show this error on browser:
Blocked autofocusing on a form control in a cross-origin subframe.
This seems to be a cross-domain issue,but I can’t found any setting to fix it. If you has any idea, please tell me. thanks you.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Blocked autofocusing on a form control in a cross-origin ...
Using Chrome, when I'm trying to change values of an input located in an IFrame of another app on our server, I get...
Read more >Blocked autofocusing on a form control in a cross ... - GitHub
Actual behavior: The rocket Chat is giving us a cross error tryLogin. Blocked autofocusing on a form control in a cross-origin subframe.
Read more >Blocked autofocusing on a form control in a cross ... - Syncfusion
Forum Thread - Blocked autofocusing on a form control in a cross-origin subframe. - JavaScript - EJ 2.
Read more >Error Blocked autofocusing - Development - Rocket Chat forums
This error is caused by an input element (Username input of the login page for me) that has “autofocus” set to on. You...
Read more >Autofocus form control in iframe - JSFiddle - Code Playground
Blocked autofocusing on a form control in a cross-origin subframe. 2. document.querySelector('input').focus();. CSS Tidy. xxxxxxxxxx.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t know if this helps you guys, but I wanted to give you guys some more information.
I access home assistant by https://ha.mydomain.inside:8123. I accessed VS Code by https://vscode.mydomain.inside When I have:
This configuration exhibited the problem described above.
Here’s what I did yesterday:
So, since both Home Assistant and code-server are not running with the same hostname (ha.mydomain.inside), the problem goes away.
i have perhaps the same issue : impossible to login