Web API 13 Mar 2006 Present RB, ID, GE, MH, DJ, CJ, SS, AK, DS, JS Chair RB Scribe MH Topics action items open issues spec status F2F meetings Back to open issues action items action-11 anne to draft something for next week action-12 robin will prod SVG WG action-22 underway action-25 underway action-29 done action-30 done action-31 open action-33 started discussion, ongoing action-34 open action-35 done action-37 done, dean will set up tracking action-6 ongoing action-24 ongoing, will work on it this week SS: if we track other lists aren't there some risks of confusing trackbot with the ACTION references belonging to other lists ? (or are we the only to use a trackbot) ? ACTION: GE Check how Opera deal with DOMAttrModified when change affect .prefix .specified action-38 ongoing, will work on it this week action-39 ongoing, will raise with SVG this week or next AK: I talked with SVG about XHR AK: During the W3C TP AK: It seems that they are worried about referencing a specification not in LC... action-45 draft list available, not yet complete will send to WG for comments action-46 standing orders action-47 done action-48 done action-50 http://www.mnot.net/test/xmlhttprequest/ will do by end of week action-51 ongoing action-53 ongoing action-54 ongoing action-55 resolved to always accumulate ? RESOLUTION: always put RESOLUTION and RATIONALE in minutes RATIONALE: because it really helps when looking at past minutes RB: reviewed F2F minutes RB: generally concatenate except where not possible (e.g. host) JS: separator = ', ' done action-56 draft available by next week action-57 dean investigating action-58 ID: I agree RESOLUTION: must support 1 arg and should support 0 arg for the send method RATIONALE: 1 arg works in all current UAs, so that should be MUST. 0 args works in most but not all UAs, however there is a lot of content that uses 0 args so future implementations should support it action-59 this week action-60 will do this week action-61 partially done action-62 done but sent to wrong list resent action-57 again will raise issue action-64 pending action-65 pending action-67 opera compatible with mozilla will provide feedback on some issues encountered action-74 pending 2 weeks action-76 figure out when cancel event can it be redispatched ? christophe will take the action action-78 done action-81 done action-83 pending, will do by next week action-86 tried, but no response so far action-89 assign to bjoern action-90 done action-91 pending action-92 pending open issues http://www.w3.org/2005/06/tracker/webapi/issues/open issue-10 pending charles issue-23 issue-24 GE: don't rely on ECMA spec because changes are coming JS: want to align with next version of ECMA spec but how if its not available yet GE: say that it throws an exception but not specify what ? issue-26 SS: use case, [member private only] ACTION: DS to take ISSUE-26 to the public issue-27 GE: need to look at on a case by case basis RB: null will raise an exception unless otherwise specified RESOLUTION: null is disallowed in D3EV whenever it does not clearly say that it's allowed RATIONALE: there is no generic rule RESOLUTION: we should add a DOMException code for NULL_NOT_ALLOWED_ERR RATIONALE: we can add codes, and it's useful AK: I wonder if the null namespace is similar to the empty string namespace... ACTION: GE to draft text for NULL_NOT_ALLOWED_ERR (or better name) ACTION: BH to check that D3EV specifies that parameters are nullable whenever they are specs status XHR status AK: Waiting for input from Dean (intro, status etc) RB: AK, you don't need input from Dean, move on AK: ok, I'll have something by next week Window API ID: draft for review resent to mailing list, ready for discussion. Now has 1 interface for window F2F meetings DS: Is there somewhere where all the dates etc are shown - on the wiki ? ACTION: CM to add F2F information to the WG's wiki Back to open issues issue-29 http://www.w3.org/2005/06/tracker/webapi/issues/29 ACTION: JS to write a test case for the complicated (multiwindow) situations with uri resolution in open()