- From: <bugzilla@jessica.w3.org>
- Date: Wed, 30 Apr 2014 04:10:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25405
--- Comment #3 from spiritRKS1910 <crimsteam@gmail.com> ---
I check this more closely and:
===
In initCompositionEvent()
DOMString? locale >> should be change to DOMString locale
Created untrusted event (with locale = null in initCompositionEvent or
constructor) and getting e.locale return string.
<script>
var ev = document.createEvent("CompositionEvent");
ev.initCompositionEvent("hellow", true, true, window, null, null);
document.write(ev);
document.write("<br>");
document.write(ev.locale === null); // false (IE/Firefox, Chrome doesn't
suport .locale)
</script>
===
.data is more interesting, now we don't have suport it on InputEvent interface,
but work in CompositionEvent interface (in FF, Chrome, IE).
Below works only in Chrome
<script>
var ev = new CompositionEvent("hello", {
data: null
});
document.write(ev);
document.write("<br>");
document.write(ev.data === null); // false
</script>
Below works in Chrome/IE and Firefox
<script>
var ev = document.createEvent("CompositionEvent");
ev.initCompositionEvent("hellow", true, true, window, null, null);
document.write(ev);
document.write("<br>");
document.write(ev.data === null); // false (IE/Chfome), true (Firefox)
</script>
Only Firefox respect nullable and I wonder if it should be for some reason, or
just a small mistake in the specification that has been implemented.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 30 April 2014 04:10:03 UTC