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

Specify the arguments of initCompositionEvent() #134

Open
foolip opened this issue Feb 23, 2017 · 6 comments
Open

Specify the arguments of initCompositionEvent() #134

foolip opened this issue Feb 23, 2017 · 6 comments

Comments

@foolip
Copy link
Member

foolip commented Feb 23, 2017

initCompositionEvent() is supported in Blink, EdgeHTML, Gecko and WebKit. Usage is very low but it's still not a good use of time trying to remove it from all engines.

Instead, specify it like this:

void initCompositionEvent(DOMString type,
                          optional boolean bubbles = false,
                          optional boolean cancelable = false,
                          optional Window? view = null,
                          optional DOMString data = "");

See also whatwg/dom#387

@foolip
Copy link
Member Author

foolip commented Feb 23, 2017

@smaug----, do you have a plan for Gecko's locale member/argument? I didn't include it here.

@smaug----
Copy link

Hmm, I don't now remember why we have .locale.
@masayuki-nakano might.

@foolip
Copy link
Member Author

foolip commented Mar 9, 2017

@garykac, might you find time to work on this?

@masayuki-nakano
Copy link

I have no idea how to implement "locale" attribute for representing native events because it's difficult to map each OS's locale and locale attribute value. If we cannot standardize the mapping solidly in the spec, same IME's locale may be different between browsers and OSes.

@garykac
Copy link
Member

garykac commented Mar 9, 2017

Basically what @masayuki-nakano said.

We wanted to do locale, because we feel it would be useful, but we know that it will be a lot of work to specify it properly and we don't have the time to devote to it right now.

@foolip
Copy link
Member Author

foolip commented Mar 9, 2017

OK, for the purposes of this issue we can pretend that locale doesn't exist, just wanted to make sure omitting it wouldn't be a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants