See also: IRC log
<scribe> ACTION: Dom to review the DOM Level 2 Style sheet test case proposed by wilhelm [recorded in http://www.w3.org/2008/06/24-mwts-minutes.html#action06] [DONE]
Dom: looks technically good, but not sure it is specific to mobile enough to deserve being included
Wilhelm: it is not mobile
specific, indeed; a generic test for style sheets DOM
... but they are pretty useful for various web applications
Dom: but is there a strong need for using dom style sheets support from the community?
Wilhelm: I don't have a strong opinion for this particular feature - but think we should test for DOM Level 2 support
Dom: ok, let's go with that one for the next release
Kai: I'm struggling to see the
use cases for DOM style sheets - which web apps want to use it
or do use it?
... manipulating style from scripts seems like breaking the
separation between presentation/logic
Wilhelm: make sense; probably should test for something else then... Any suggestion?
Kai: I'm interested in events in general
Dom: what about Mutation events?
they are part of DOM Level 3 events, (not a rec, but quite
stable)
... they seem to be quite useful
Kai: yeah, that's what I had in mind
Wilhelm: sounds good
<scribe> ACTION: Kai to propose a test case around DOM mutation events [recorded in http://www.w3.org/2008/07/01-mwts-minutes.html#action02]
<scribe> ACTION: Kai to propose an updated AJAX test with onload (or other event) added [recorded in http://www.w3.org/2008/06/24-mwts-minutes.html#action07] [DONE]
Kai: I added a window.onload()
call to xhtmlhttprequest.js
... a one-line change
http://static.webvm.net/wct/xmlhttprequest.js
Kai: is window.onload standard?
Dom: I think you're supposed to put the onload event on the body element
e.g. body = document.getElementByTagName("body")[0]
<wilhelm> <body onload='foo()'>
body.onload("foo")
<hendry> http://git.webvm.net/?p=wct;a=commitdiff;h=ffceaad60e690600b2f56fd43755fe7e77da38ed
<hendry> <body onload="callXMLFile()">
<hendry> window != body
<scribe> ACTION: Kai to update the onload event in xhtmlhttprequest.js [recorded in http://www.w3.org/2008/07/01-mwts-minutes.html#action04]
http://www.w3.org/TR/2006/WD-Window-20060407/
<hendry> <body onload="callXMLFile()"> is very common (i see it all the time)
Dom: you also have a proposed update to the cookies test
Kai: mostly a js-lint clean up of the test
<hendry> http://git.webvm.net/?p=wct;a=commitdiff;h=1deec9ed09888d858511130b42e0ab623a665867
Wilhelm: plus the unicode thing, right?
Kai: looking at the cookies RFC,
the acceptable documentations are quite interesting
... wondering whether we should target these
... maybe that's going too far
... I think cookies support is one of the things were bad
browsers can react pretty badly
dom: sounds like a good idea in
general, but maybe not in the WCTMB?
... I would support building a set of test cases around cookies
after we're done with WCTMB
... Wilhelm, what do you think about unicode based cookies?
Wilhelm: not sure
Kai: your original test used "escape" - I think it is deprecated
http://dev.w3.org/cvsweb/~checkout~/2008/mobile-test/cookie.js?rev=1.2&content-type=text/plain
<scribe> ACTION: Wilhelm to update cookies test based on Kai's suggestions [recorded in http://www.w3.org/2008/07/01-mwts-minutes.html#action05]
<scribe> ACTION: Dom to request a CVS account for Kai [recorded in http://www.w3.org/2008/07/01-mwts-minutes.html#action06]
[Kai, BTW, you suggested the removal of the data: uri test: http://lists.w3.org/Archives/Public/public-mwts/2008Apr/0005.html :) ]
Kai: what about the data: uri test? do you think that's a good idea
Wilhelm: we could include it as part of the canvas test
dom: I would support having this as part of the canvas test
<scribe> ACTION: Wilhelm to update canvas test to use data: URL scheme [recorded in http://www.w3.org/2008/07/01-mwts-minutes.html#action07]
Kai: I've also noticed data-attribute being discussed on HTML5
dom: probably too early for inclusion in the test
http://www.cloudfour.com/36/mobile-browser-concurrency-test/
Dom: a performance test for
mobile browsers
... is performance a good topic for our next deliverable?
Wilhelm: sounds good
Kai: +1
Dom: next meeting on July 22nd