See also: IRC log
<MarkS> I thought it was tap dancing
<wellsk> sorry
:-)
<_lars> hm, zakim isn't working very well for me today... I'll try another number
<Charlie> * yes, could i suggest one based on the IBM approved list?
<Charlie> * i can send email in a bit
<Nick> don't know if it related but david posted some remarks to the test suite
<Nick> (on www-forms)
<wellsk> http://www.w3.org/MarkUp/Forms/Test/XForms1.0/Edition3/front_html/XF103edTestSuite.html
<Nick> no time
<Nick> a date not without time
<Nick> 2002-09-24+06:00
<Nick> I think ;)
<Nick> so a date with time zone
<Nick> now: data + time + time zone
<MarkS> I'll ask David
<Nick> there is an example for local-time
<markbirbeck> on the previous discussion...surely now() *doesn't* return the 'local time', since it is first normalised to UTC. So if it's 1pm in somewhere that is 8 hours behind London, won't now() give 21:00?
<Nick> I think it should be in the default stylesheet we talked about
<Nick> don't know in which state the default css is?
<Nick> it does have an effect
<Nick> I think you want to style invalid values
<Nick> just like you want to style required by default
<klotz> is this the resolution: required and invalid fields should be presented specially, and form authors should have control over presentation and processors may vary the presentation style and time and processors should use CSS if it is available.
looks good
<Nick> http://www.w3.org/TR/2007/WD-xforms11-20070222/#rpm-init
<Nick> Perform the behaviors of xforms-rebuild, xforms-recalculate, and xforms-revalidate in sequence on this model element without dispatching events to invoke the behaviors.
<Nick> The notification event markings for these operations are discarded, and the xforms-refresh behavior is not performed since the user interface has not yet been initialized.
<klotz> phone died
darn
Mark: I agree that it is odd that
the CSS treatment and the event treatment happen
differently
... it used to be different to this
<klotz> it wont letme join
Erik: We optimise this case
... but if you have 400 controls, there will be quite a lot of
events
Mark: We want to do save and
resume, and so we need the initialization events
... so I agree strongly with you , and we should reinstate this
(I hadn't realised it was gone)
Nick: I think it was an erratum on 1.0
<klotz> i have posted a use case for xforms-value-changed on instance replace, to handle "errors" dpeending on the returned instance.
Mark: I think it is a side-effect of the change to refresh
<Charlie> MIP events but not value-changed, yes
Mark: We can't resolve this now.
Need John to tell us whether it was changed by mistake
... let's put this off to the FtF
<jturner> bye
<_lars> bye
Steven: So resolved
<Nick> bye
This is scribe.perl Revision: 1.128 of Date: 2007/02/23 21:38:13 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven WARNING: No "Topic:" lines found. Default Present: wellsk, Steven, MarkS, Nick_van_den_Bleeken, Charlie, markbirbeck, Leigh_Klotz, +9308322aaaa, ebruchez, jturner, _lars, +1.541.754.aabb, Blake Present: wellsk Steven MarkS Nick_van_den_Bleeken Charlie markbirbeck Leigh_Klotz +9308322aaaa ebruchez jturner _lars +1.541.754.aabb Blake Agenda: http://lists.w3.org/Archives/Public/public-forms/2007Aug/0082 WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 29 Aug 2007 Guessing minutes URL: http://www.w3.org/2007/08/29-forms-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]