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

Missing document.execCommand()? #37

Open
kylewolfe opened this issue May 22, 2017 · 4 comments · May be fixed by #39
Open

Missing document.execCommand()? #37

kylewolfe opened this issue May 22, 2017 · 4 comments · May be fixed by #39

Comments

@kylewolfe
Copy link

How would the equivalent of document.execCommand() be achieved in this library?

@dominikh
Copy link
Owner

/cc @shurcooL

@dmitshur
Copy link
Collaborator

dmitshur commented May 22, 2017

From looking at the API of this library, it appears it does not currently have support for execCommand.

If your question is "how would the equivalent of document.execCommand() be achieved in general", I don't know, that requires investigation. It's not a priority for me at this time, so I'm not working on it.

If you're interested in working on this, feel free to look into it.

@udhos
Copy link

udhos commented Jun 30, 2017

I am using this as work-around:

js.Global.Get("document").Call("execCommand", "copy") // document.execCommand('copy');

@dmitshur
Copy link
Collaborator

dmitshur commented Jun 30, 2017

Thanks @udhos, that sounds like the right solution. We can add an ExecCommand method that uses such an implementation. Whoever is interested in getting this added to dom can send a PR.

@udhos udhos linked a pull request Jun 30, 2017 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants