XHTML2 Working Group Teleconference -- 20 Jan 2010

<trackbot> Date: 20 January 2010

<alessio> hi all :)

<oedipus> hi, steven! my reader says your myOpera pic would make a great dust cover author's photo or a very cool CD cover

<Steven__> :-)

<Steven__> Yes, it is a nice photo

<Steven__> My phone was in the charger all night, but it hadn't made contact! Grrr. Now I have to work out what to do...

<oedipus> note the one-off zakim passcode for today 26631

<Steven__> Just thinking

<oedipus> can you skype in?

<Tina> The passcode is NOT the one in the agenda?

<Steven__> It's in the channel topic Gregory

<Steven__> Oh damn!

<Steven__> Sorry I for got to change the agenda

<Steven__> I'll try my mobile to see if it will work....

<oedipus> tina, 26631

<oedipus> tina, +1 617 761 6200 or +44.117.370.6152

<Tina> oedipus: I've never heard of any such assignment.

<Tina> oedipus: Thank you

<oedipus> shane, 26631

<ShaneM> I was trying to get the phone number for Tina

<oedipus> scribe: Gregory_Rosmaita

<oedipus> scribenick: oedipus

<Tina> oedipus: Indeed, as on mobile phones in Europe. But 'CONF1' does not translate to '26631' on that system *shrugs*

Role and Access Modules - future of

http://www.w3.org/WAI/PF/wiki/Role

http://www.w3.org/WAI/PF/wiki/Role/Vocab

http://www.w3.org/WAI/PF/wiki/Talk:Role/Vocab

http://www.w3.org/WAI/PF/HTML/wiki/Access

http://www.w3.org/WAI/PF/HTML/wiki/Access/element_versus_module

<Steven__> scribe: Steven__

Gregory: I just posted a bunch of links.

PFWG are picking up role

scribe: but we are waiting for Judy Brewer WAI direcvtor
... to OK it
... I have taken the last draft, and updated it
... such as renaming
... can't make it public until admin things are done
... I don't want to lose momentum
... ARIA is going to LC in Feb
... and I want to keep pace with ARIA
... Questions: the vocab document
... I understand that there is shared ownership

Shane: Yes

Gregory: What predefined roles do we need?
... I think we need 'form'

<oedipus> http://www.w3.org/WAI/PF/wiki/Talk:Role/Vocab

Gregory: Some problems there, minor but need clearing up

Steven: Send me the details, I have write access. I can make the editorial corrections

<oedipus> ACTION: Gregory - send editorial changes to Steven for Vocab document [recorded in http://www.w3.org/2010/01/20-xhtml-minutes.html#action01]

<trackbot> Created ACTION-108 - - send editorial changes to Steven for Vocab document [on Gregory Rosmaita - due 2010-01-27].

Gregory: Access is in a similar state

<oedipus> http://www.w3.org/WAI/PF/HTML/wiki/Access

Steven: It has been accepted?

<oedipus> http://www.w3.org/WAI/PF/HTML/wiki/Access/access_key_requirements

<oedipus> http://www.w3.org/WAI/PF/HTML/wiki/Access/element_versus_module

<oedipus> http://www.w3.org/WAI/PF/HTML/wiki/Access/comand_and_event#Keyboard_Focus_Attributes_Module

Gregory: We agree that we need it, and the HTML WG has asked us for a strategy
... so I would like to take the access draft as basis
... one thing we need to deal with is that DOM3 events is deprecating DOMActivate for click
... apparently click now means everything that DOMActivate used to mean
... I don't like it, but the numbers are against me.

<oedipus> SP: hit RETURN in form generate "click"

<oedipus> GJR: my understanding yes

Steven: So does [return] in a form field generate a 'click'?

<oedipus> TH: click is used in sweedish to specify a mouse-click

TIna: I can confirm that 'click' means a mouse click in Norwegian and Swedish languages, so I agree that it doesn't make anything clearer

Shane: I think that Doug Schepers's reasoning makes sense
... this is a strategy to get to interoperability

Steven: My worry is that if DOMActivate goes away, it will break handlers waiting for that event

Tina: It probably won't go away

Shane: They are saying that it is best practice

Tina: I don't think that this has been well thought through
... but I doubt there is anything we can do about it

Steven: Does Access use DOMActivate?

Shane: No, it uses the word Activate, without referring to DOMActivate

<oedipus> hives check click for DOMActivate from DSchepers: http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0004.html

Steven: It will probably affect XForms more than anything, since XForms uses DOMActivate everywhere.
... It looks to me like this would be a great HCG topic...

Gregory: Agree

<scribe> ACTION: Steven to raise DOMActivate with HCG [recorded in http://www.w3.org/2010/01/20-xhtml-minutes.html#action02]

<trackbot> Created ACTION-109 - Raise DOMActivate with HCG [on Steven Pemberton - due 2010-01-27].

Pers

Steven: There's a 404
... that needs to be fixed before we can announce

Shane: I will fix

XHTML2 draft

http://www.w3.org/MarkUp/2010/ED-xhtml2-20100113/introduction.html#s_intro

Shane: What do we do about the issues?

http://www.w3.org/MarkUp/2010/ED-xhtml2-20100113/introduction.html#sec_1.4.

<oedipus> from Web Forms 2: The default action of the click event in this case is to fire a DOMActivate event, and the default action of the DOMActivate event is to fire the change event (assuming the activation did change the value).

<oedipus> s/in Scandanavian languages/Sweedish and Norwegian

Gregory: I think we should take the issues out, make it easier to read

Stefven: Idea! How about dropping them from the spec, and then creating a DoC sort of document that just contains the open issues?

Shane: That would be easy.

<oedipus> GJR: plus 1

Shane: works for me. We can link to it.

Steven: So resolved then

AOB?

Steven: None, adjourn

Works!

Thanks

<Tina> Phew. One issue off the todo-list ...

<Tina> No, thank you :)

<inserted> scribenick: Steven__

s/scribe: steven/scribe: Steven________/

- DRAFT -

XHTML2 Working Group Teleconference

20 Jan 2010

Attendees

Contents

Role and Access Modules - future of

Pers

XHTML2 draft

AOB?

Summary of Action Items

Scribe.perl diagnostic output