Last Comment Bug 742200 - optional jsval arguments ('any' in the IDL) should become JSVAL_VOID, not JSVAL_NULL, when there was no argument passed
: optional jsval arguments ('any' in the IDL) should become JSVAL_VOID, not JSV...
Product: Core
Classification: Components
Component: DOM (show other bugs)
: Trunk
: x86 Mac OS X
: P2 normal (vote)
: mozilla14
Assigned To: Boris Zbarsky [:bz]
Depends on:
Blocks: ParisBindings
  Show dependency treegraph
Reported: 2012-04-03 22:05 PDT by Boris Zbarsky [:bz]
Modified: 2012-04-11 09:04 PDT (History)
3 users (show)
bzbarsky: in‑testsuite?
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Like so (674 bytes, patch)
2012-04-09 13:24 PDT, Boris Zbarsky [:bz]
peterv: review+
Details | Diff | Splinter Review

Description Boris Zbarsky [:bz] 2012-04-03 22:05:58 PDT
Right now we do JSVAL_NULL converted to the argument type for all optional arguments without a default value.
Comment 1 Boris Zbarsky [:bz] 2012-04-09 13:24:12 PDT
Actually, I think we can just use JSVAL_VOID across the board here; for everything but string arguments it's identical, and for string arguments I think the JSVAL_VOID behavior is more per spec.
Comment 2 Boris Zbarsky [:bz] 2012-04-09 13:24:47 PDT
Created attachment 613374 [details] [diff] [review]
Like so
Comment 4 Matt Brubeck (:mbrubeck) 2012-04-11 09:04:30 PDT

Note You need to log in before you can comment on or make changes to this bug.