-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Add document.ExecCommand(). #39
Open
udhos
wants to merge
1
commit into
dominikh:master
Choose a base branch
from
udhos:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
valueArgument
is documented at https://developer.mozilla.org/en-US/docs/Web/API/Document/execCommand as:So I don't think we can use
string
type for it, because it wouldn't be possible to specify null.We can use either
*string
, orinterface{}
and document that it needs to be astring
ornil
.@dominikh, do you have thoughts on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All I can tell is this use case worked for me:
dom.GetWindow().Document().ExecCommand("copy", false, "") // document.execCommand('copy');
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not surprised. Most JavaScript APIs will "work" when given input other than their documentation says they expect.
But I still think we should follow the documentation precisely here. Otherwise, people who look at this Go API will have questions raised in their minds, like "does this actually work despite not matching what the JS API expects?" and "will there be unintended side-effects if I don't follow the JS API documentation precisely?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will
""
ever be a valid argument? In a lot of other places, it is not, so we special-case""
in the code to act as null. See for examplewindow.GetComputedStyle
. – I'd rather not see us use*string
orinterface{}
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't expect blank string to be a valid argument, but I haven't formally verified.
If there's already precedent for using
""
when it's not a valid value to indicate something else (null
), then that should be okay.However, after briefly looking, it appears blank string may be a valid argument for
insertText
. It's not necessarily a no-op either, because it deletes selection. AlsoinsertHTML
.Is the reason to push back against
*string
because it's a hard to use API?In that case, how about
*ExecCommandArgument
, whereExecCommandArgument
is astruct{ Value string }
.Or we can add logic to treat that parameter differently based on command name.