Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blocked autofocusing on a form control in a cross-origin subframe. #1479

Open
saviorZSC opened this issue Apr 2, 2020 · 10 comments
Open

Blocked autofocusing on a form control in a cross-origin subframe. #1479

saviorZSC opened this issue Apr 2, 2020 · 10 comments
Labels
needs-investigation This issue needs to be further investigated

Comments

@saviorZSC
Copy link

Hi:
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.

@kylecarbs
Copy link
Member

Could you try with the latest release?

@kylecarbs kylecarbs added the waiting-for-info Waiting for more information from submitter label Apr 9, 2020
@kylecarbs
Copy link
Member

Closing for inactivity. Happy to help though, if you are still experiencing the problem be sure to let us know!

@merdely
Copy link

merdely commented Jan 17, 2021

I am having this problem as well and would love to troubleshoot this if you can help.

@code-asher
Copy link
Member

code-asher commented Jan 19, 2021 via email

@merdely
Copy link

merdely commented Jan 19, 2021 via email

@code-asher
Copy link
Member

code-asher commented Jan 19, 2021 via email

@nhooyr
Copy link
Contributor

nhooyr commented Jan 21, 2021

Will reopen as well.

@nhooyr nhooyr reopened this Jan 21, 2021
@nhooyr nhooyr added needs-decision and removed waiting-for-info Waiting for more information from submitter labels Jan 21, 2021
@merdely
Copy link

merdely commented Feb 6, 2021

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:

panel_iframe:
  vscode:
    title: VS Code
    url: "https://vscode.mydomain.inside"
    icon: si:visualstudiocode

This configuration exhibited the problem described above.

Here's what I did yesterday:

  1. Created an nginx virtual host entry for ha.mydomain.inside on port 443
  2. Added the following for vscode under that virtual host entry:
  location /code-server/ {
    # "vscode:8080" is my nginx Docker instance connecting to my code-server Docker instance using Docker Compose
    proxy_pass http://vscode:8080/;
    # more nginx proxy options here
  }
  1. Updated my Home Assistant configuration with:
panel_iframe:
  vscode:
    title: VS Code
    url: "https://ha.mydomain.inside/code-server/"
    icon: si:visualstudiocode

So, since both Home Assistant and code-server are not running with the same hostname (ha.mydomain.inside), the problem goes away.

@jsjoeio jsjoeio added this to the Backlog milestone Apr 29, 2021
@jsjoeio jsjoeio modified the milestones: Backlog, Backlog Candidates May 14, 2021
@jsjoeio jsjoeio added needs-investigation This issue needs to be further investigated and removed needs-decision labels May 14, 2021
@stale
Copy link

stale bot commented Nov 10, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.

@stale stale bot added the stale label Nov 10, 2021
@stale stale bot closed this as completed Nov 16, 2021
@warlordattack
Copy link

i have perhaps the same issue : impossible to login
2022-07-17_145025

@code-asher code-asher reopened this Jul 18, 2022
@code-asher code-asher removed the stale label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-investigation This issue needs to be further investigated
Projects
None yet
Development

No branches or pull requests

7 participants