This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Since WindowModal.returnValue is a DOMString and defaults to the empty string, I don't see any way for a non-string type to be returned. In general, |any| in WebIDL is yucky.
Actually, my testing in [1] indicates that Gecko, Chrome, and IE all currently support passing arbitrary objects as returnValues. So presumably it's the WindowModal IDL that needs to change. [1] - http://people.mozilla.com/~bholley/testcases/xomodal.html
Checked in as WHATWG revision r7976. Check-in comment: WindowModal.returnValue isn't limited to strings. http://html5.org/tools/web-apps-tracker?from=7975&to=7976
This isn't enough, I don't think: * We need to spec the security check to returnValue, which should be isomorphic to that of dialogArguments. * returnValue should probably default to undefined, rather than the empty string. (Sorry if reopening the bug isn't correct etiquette here - is a followup preferred?)
Reopening is absolutely fine, please don't hesitate to reopen bugs I screw up! I've tried to make returnValue's logic match Firefox's behaviour, at least insofar as it is demonstrated by these demo tests (001-004): http://www.hixie.ch/tests/adhoc/dom/level0/window/showModalDialog/
Checked in as WHATWG revision r8008. Check-in comment: Make showModalDialog()'s returnValue logic more closely match Firefox. Previously it matched nobody. None of the browsers match each other. Firefox's behaviour seems the sanest. http://html5.org/tools/web-apps-tracker?from=8007&to=8008
This looks great. Thanks. :-)