W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2009

Minutes, DOM3 Events Telcon, 24 June 2009

From: Doug Schepers <schepers@w3.org>
Date: Wed, 24 Jun 2009 18:02:53 -0400
Message-ID: <4A42A28D.1050206@w3.org>
To: www-dom@w3.org
Hi, DOM3 Events fans-

The minutes for the DOM3 Events telcon of 24 June 2009 can be found here:

  http://www.w3.org/2009/06/24-webapps-minutes.html

Or as text below:

    [1]W3C

       [1] http://www.w3.org/

                                - DRAFT -

              Web Applications Working Group Teleconference

24 Jun 2009

    See also: [2]IRC log

       [2] http://www.w3.org/2009/06/24-webapps-irc

Attendees

    Present
           Shepazu, dand, MSjacob, smaug

    Regrets
    Chair
           SV_MEETING_CHAIR

    Scribe
           Travis

Contents

      * [3]Topics
          1. [4]IME events from DOM Mailing list
          2. [5]Method for asking the UA for what keys have been pressed
             down.
      * [6]Summary of Action Items
      _________________________________________________________



    <trackbot> Date: 24 June 2009

    <dand> hey guys

    <shepazu> hi, dand

    <dand> how's it going

    <dand> is there a www-dom telecon now? or next week?

    <shepazu> the chair forgot to send out the agenda, so I'm not sure
    who's going to show

    <dand> no probs

    <dand> should i dial in? or hang out here and wait first

    <shepazu> I'm on the line, but if we don't have a few other people
    show up in the next 10 minutes, we should postpone until next week

    <dand> ok

    <shepazu> well, if you can call in, I can bring you up to speed

    <shepazu> trackbot, code?

    <trackbot> Sorry, shepazu, I don't understand 'trackbot, code?'.
    Please refer to [7]http://www.w3.org/2005/06/tracker/irc for help

       [7] http://www.w3.org/2005/06/tracker/irc

    <dand> can't hear you guys too great

    <shepazu>
    [8]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/proposals/

       [8] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/proposals/

    Short telecon today

    shepazu: Recap: goal of the different key event flows is to find a
    harmoneous graph that best for user agents.

    <shepazu> Travis: scribenick

    <shepazu> scribenick: Travis

    shepazu: Not likely to spec (solve) the IME model.
    ... Planning to publish the different models as appendices to the
    spec.
    ... Key models missing the mutation event points (where they fire)
    or where the DOM is modified (in user agents without mutation
    events)
    ... Still need to hear from WebKit.

    dand: I think Webkit's model is probably pretty close to Trident's
    ... I have some people that I could contact.

    <dand> yep

IME events from DOM Mailing list

    shepazu: Some disccusion on the mailing list regarding IME.

    Travis: two problems that they wanted to solve.
    ... the composition box appears in random places and can occude
    important web page elements (like search suggestions)
    ... other is that all user agents should implement compositionstart
    and compositionend events. Though, I'm not sure why?

    dand: Not necessarily that those physical events are important, but
    that they do what you need...
    ... only get fired for IME inputs (don't necessarily have to do with
    key events).
    ... In IE you don't get notified of some events...
    ... using voice or other you may get spotty notification.
    ... Firefox's compositionstart event allows you to change the DOM
    and place the cursor in a new location, then the actual input will
    occur in the new location.
    ... nice to grap input and contain it to a particular place in the
    DOM.
    ... In general, knowing when the composition finishes is useful
    because you can respond to user activity when the fully composed
    string.

    <shepazu>
    [9]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events
    .html#events-Events-TextEvent

       [9] 
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-TextEvent

    Travis: Does the textInput event handle these use cases...?

    dand: compositionend could be like textInput, but the
    compositionstart event is still important.

    <dand> [10]http://www.danilatos.com/event-test/ExperimentTest.html

      [10] http://www.danilatos.com/event-test/ExperimentTest.html

    shepazu: textInput does not say where the textInput came from. Maybe
    it could (IME, key, voice, etc.)?
    ... (random idea) for positioning of the IME candidate window, we
    could possibly put an X/Y event for where the IME window came up...

    dand: Hmm, maybe this could get more complicated...

    shepazu: We'll see if implementors want to do that. Don't want to
    jump into UI necessarily..

    <shepazu>
    [11]http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-June/02
    0553.html

      [11] 
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-June/020553.html

    dand: TSS is the API for IME. Browsers may not support these fully,
    and could through complications into the mix.

    <dand> TSF

    dand: IMM32 (old one), TSF (new one), others for mac/linux

    <smaug> ( [12]https://bugzilla.mozilla.org/show_bug.cgi?id=88831 )

      [12] https://bugzilla.mozilla.org/show_bug.cgi?id=88831

    Travis: I don't think we should go down the road of trying to spec
    all of the details of what an IME event model could look like

    dand: seems very complicated to purse that and we lack
    implementation experience.

    shepazu: OK. Sounds good. We should spec a minimum of
    compositionstart/end for IME because that's what browsers have
    chosen to do.

Method for asking the UA for what keys have been pressed down.

    shepazu: We talked about this last week, and several folks throught
    there was utility there.
    ... That's about it for that topic :)
    ... dand can you see about connected us with the WebKit guy for
    compositionstart/end events?

    <shepazu> trackbot, end telcon

Summary of Action Items

    [End of minutes]
Received on Wednesday, 24 June 2009 22:03:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:00 GMT