[D3E] Draft minutes from 15 July 2014 call

The minutes from the July 15 D3E call are in the following (and copied 
below):

    <http://www.w3.org/2014/07/16-webapps-minutes.html>

-AB

    [1]W3C

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

                                - DRAFT -

                             SV_MEETING_TITLE

16 Jul 2014

Attendees

    Present
    Regrets
    Chair
           SV_MEETING_CHAIR

    Scribe
           garykac

Contents

      * [2]Topics
      * [3]Summary of Action Items
      __________________________________________________________

    <masayuki> garykac: hi

    hello

    Not much has changed since last week.

    I still have to update the spec to match the discussion from
    last week.

    <masayuki> Yeah, I'm waiting the spec update for requesting
    review of patches.

    Sorry about the delay..

    We got an email from someone asking about including the
    KeyboardEvent context with the Input event.

    So that you could tell that a keyboard event caused the input
    event without having to listen to both events.

    I'm not sure that it's necessary since it's not that hard to
    listen to both events.

    He referred to :
    [4]http://stackoverflow.com/questions/9906885/detect-backspace-
    and-del-on-input-event#comment-27372628

       [4] http://stackoverflow.com/questions/9906885/detect-backspace-and-del-on-input-event#comment-27372628

    <masayuki> Hmm, I don't think that we should do it because even
    if web apps implement such text editor, which must not work
    with some input devices which don't cause keyboard event.

    <masayuki> It's just well known behavior that "Backspace" is
    deleting previous character of a caret and "Delete" is deleting
    next character of a caret.

    Unless there is text currently selected...

    <masayuki> However, e.g., on Mac, some users might have
    customized of the keybindings of "Backspace" or "Delete".

    <masayuki> Yes.

    <masayuki> Only with D3E, web developers cannot know what
    should happen at editing text of each key without transpalent
    <input> or <textarea>...

    <renoirb> ooh :)

    <masayuki> I guess, in the future, keyboard event should have
    |.action| or |.command|. Then, web apps can create their own
    text editor with native keybindings of the users environment.

    Is it a problem that web devs needs to add a transparent
    input/textarea in order to track all the keys when editing
    text? I'm not sure how common this is (or if it requires
    additional info to make it easier).

    <masayuki> I'm not sure if there are problems and such new
    attributes actually improve/solve them.

    <masayuki> We need comments from actual web developers...

    Yeah. I'd rather not add any complexity unless it's solving a
    real problem.

    I haven't heard a lot of call for this, but I'm not sure how
    many webdevs are tracking the spec.

    <masayuki> Anyway, I think that InputEvent should be nutral
    from input device.

    Yep that sounds good to me as well. I wouldn't mind having
    optional fields, but only if it's solving a problem.

    Anyway, it doesn't seem like we have much to do today. We don't
    need to meet every week for now. How about in two weeks?

    <masayuki> Indeed. Web developers should request more features
    for the future's web ;-)

    ^_^

    <masayuki> I'm okay to meet every two weeks.

    <masayuki> I'll file spec bugs when I find issues, though.

Summary of Action Items

    [End of minutes]

Received on Wednesday, 16 July 2014 11:04:39 UTC