Clipboard API: Proposal for asynchronous API

I just sent a proposal to the WICG for an asynchronous Clipboard API: https://discourse.wicg.io/t/proposal-modern-asynchronous-clipboard-api/1513 (yes, I know. Not the first time something like this has been proposed )

Re: [clipboard] kill onbefore* events?

On Wed, Mar 9, 2016 at 3:40 PM, Hallvord Reiar Michaelsen Steen < hst...@mozilla.com> wrote: > > On Wed, Mar 9, 2016 at 11:19 PM, Gary Kacmarcik (Кошмарчик) > <gary...@chromium.org> wrote: > > > There is a design tension between the 2 extreme approaches, each with &

Re: [clipboard] kill onbefore* events?

On Wed, Mar 9, 2016 at 5:29 AM, Hallvord Reiar Michaelsen Steen < hst...@mozilla.com> wrote: > On Mon, Mar 7, 2016 at 11:00 PM, Gary Kacmarcik (Кошмарчик) > <gary...@chromium.org> wrote: > > > Agreed. That is the major benefit of 'beforeinput' and 'input' -- you > w

Re: [clipboard] kill onbefore* events?

On Mon, Mar 7, 2016 at 12:49 PM, Johannes Wilm wrote: > > On Mon, Mar 7, 2016 at 3:52 PM, Hallvord Reiar Michaelsen Steen < > hst...@mozilla.com> wrote: > >> >> On Mon, Mar 7, 2016 at 2:50 PM, Johannes Wilm >> wrote: >> >> > > At the beginning

Re: [clipboard] kill onbefore* events?

I'm not very familiar with onbefore{cut|paste|copy}, but they sound like very specialized versions of the beforeinput event. What do these events provide that you don't get from handling beforeinput? (well, other than the upcoming context "I'm about to do a cut/paste/copy") On Tue, Feb 2, 2016

Re: time at TPAC other than Wednesday?

-- Forwarded message -- > From: Gary Kačmarčík (Кошмарчик) <gary...@google.com> > Date: Wed, Nov 4, 2015 at 11:32 PM > Subject: Re: time at TPAC other than Wednesday? > To: Johannes Wilm <johannesw...@gmail.com> > Cc: Travis Leithead <travis.leith..

Re: PSA: publishing new WD of UI Events and D3E Keyboard specs April 28/30

On Fri, Apr 24, 2015 at 7:26 AM, Arthur Barstow art.bars...@gmail.com wrote: A few notes about these specs: * The permissions of the specs' now obsolete Github repository will be set to read-only. s/Github/Mercurial/ ?

Re: DOM L3 Events Input Events Work to the Editing Task Force

|input| and |beforeinput| were only brought into D3E because they were 1) Required since |keypress| was being deprecated (with |input|/|beforeinput| intended as a replacement) 2) Not being worked on by anyone. From that POV, it sounds like a reasonable idea. Esp. since one of the places (IIRC)

Re: CfC: publish WG Note of UI Events; deadline November 14

On Fri, Nov 7, 2014 at 7:36 AM, Anne van Kesteren ann...@annevk.nl wrote: On Fri, Nov 7, 2014 at 4:28 PM, Arthur Barstow art.bars...@gmail.com wrote: If anyone has comments or concerns about this CfC, please reply by November 14 at the latest. My concern is that we previously agreed that

Re: Proposal for a DOM L3 Events Telecon

On Tue, May 7, 2013 at 1:39 AM, Masayuki Nakano masay...@d-toybox.comwrote: Hello, sorry for the big delay due to my business trip and holiday week of Japan. I'm available on either schedule. When I join the telecon, how can I join it? Skype or something? Excellent question - I'm wondering

Re: Proposal for a DOM L3 Events Telecon

On Mon, Apr 29, 2013 at 12:59 PM, Travis Leithead travis.leith...@microsoft.com wrote: I’d like to propose we start a call to begin to work toward resolving the final bugs in the spec and for other business related to getting DOM L3 Events to CR. On the call we can workout what subsequent

Re: Proposal for a DOM L3 Events Telecon

On Mon, Apr 29, 2013 at 12:59 PM, Travis Leithead travis.leith...@microsoft.com wrote: I’d like to propose we start a call to begin to work toward resolving the final bugs in the spec and for other business related to getting DOM L3 Events to CR. On the call we can workout what subsequent

Re: publish FPWD of UI Events; deadline May 4

Google supports this. On Mon, Apr 29, 2013 at 11:03 AM, Travis Leithead travis.leith...@microsoft.com wrote: Microsoft supports this. -Original Message- From: Arthur Barstow [mailto:art.bars...@nokia.com] Sent: Saturday, April 27, 2013 7:31 AM To: public-webapps Subject: CfC:

Re: Draft minutes: 26 April 2013 f2f meeting

person = comments directly from people on IRC person: = comments transcribed from people live in the room or on the phone. On Sat, Apr 27, 2013 at 8:04 PM, Rick Waldron waldron.r...@gmail.comwrote: This is hard to follow... Almost like two different discussions are happening at the same time.

Re: CfC: publish WD of Clipboard API and events; deadline March 26

Formatting comment: There are hard-coded section numbers in the doc and respec auto-numbers the first h# tag inside section tags. The result of this is that most of the sections in this spec have 2 (different!) section numbers. It seems like the hard-coded section numbers should probably be

Re: Re: Keyboard events for accessible RIAs and Games

I've updated the UIEvents document with an initial draft for queryKeyCap/queryLocale https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm (Section 4.1) On Mon, Feb 18, 2013 at 8:09 AM, Gary Kacmarcik (Кошмарчик) gary...@chromium.org wrote: I'll be updating the document this week. I'll

Re: Re: Keyboard events for accessible RIAs and Games

I'll be updating the document this week. I'll send an update to the list after that happens. On Sat, Feb 16, 2013 at 7:40 AM, Florian Bösch pya...@gmail.com wrote: Any progress on the speccing of queryKeyCap? On Fri, Feb 1, 2013 at 9:14 PM, Gary Kacmarcik (Кошмарчик) gary...@chromium.org

Re: Re: Keyboard events for accessible RIAs and Games

On Fri, Feb 1, 2013 at 11:42 AM, Travis Leithead travis.leith...@microsoft.com wrote: I think we should give it another try by including it in our UI Events spec. I like the idea of adding the static queryKeyCap(code) API to Keyboard events. I wonder about the name though. A key capability

Re: Keyboard events for accessible RIAs and Games

This is not the first time these issues have been raised. The following threads can provide some context to the current state of the discussion: http://lists.w3.org/Archives/Public/www-dom/2012JulSep/0103.html (obsolete proposal)

Re: Keyboard events for accessible RIAs and Games

On Wed, Jan 30, 2013 at 9:31 AM, Florian Bösch pya...@gmail.com wrote: To the first comment: The persistent description might not offer a user something he recognizes. This becomes relevant in the case I'm arguing for when a Web-Developer wants to construct a mapping dialog (example

Re: Keyboard events for accessible RIAs and Games

Kacmarcik (Кошмарчик) gary...@chromium.org wrote: Yes, trying to match the current (virtual) keycap was not a direct goal, but adding the 'code' attribute makes it possible (when combined with the current layout) to calculate a keycap value. I think that would probably be the most preferable

DOM Level 3 Events - minor comments

This is a list of typos and other minor formatting problems that I encountered while going through the current DOM Level 3 Event spec. A few of the things listed here are actual errors, but the majority fall into two categories: * Initial capital letter missing at the start of a note or warning. *

Re: Re: Event.key complaints?

On Thu, Nov 8, 2012 at 6:37 AM, Hallvord Reiar Michaelsen Steen wrote: Hence, what I think would be most usable in the real world would be making event.key a mapping back to un-shifted character values of a normal QUERTY (en-US) layout. Authors are asking for stable reference values for

Re: Re: Event.key complaints?

On Fri, Nov 30, 2012 at 4:29 PM, Travis Leithead travis.leith...@microsoft.com wrote: Awesome stuff Gary. ** ** (And I like that we won't need to change the behavior of key or char in your proposal—that part made me really nervous, since IE has shipped this stuff since 9, and I know

Re: Event.key complaints?

On Thu 1 Nov 2012, Hallvord R. M. Steen wrote: I would like the story of event.char and event.key to be that event.char describes the generated character (if any) in its shifted/unshifted/modified/localized glory while event.key describes the key (perhaps on a best-effort basis, but in a way

Re: Proposal to add USB keycodes to the current DOM3 key events

On Thu, Sep 13, 2012 at 12:15 AM, Masayuki Nakano masay...@d-toybox.comwrote: Hi, I'm a developer of Gecko. So, I'd like to comments to this document. Thanks for your comments and my apologies for taking so long to respond. On 2012/09/08 3:37, Gary Kacmarcik (Кошмарчик) wrote: Problems

Re: Proposal to add USB keycodes to the current DOM3 key events

(Including the contents of entire document inline so that the info is easier to skim/comment on.) -Gary Kacmarcik (gary...@chromium.org Proposal for enhancing the current DOM Level 3 key events with USB scancodes Status: DRAFT Authors: Gary Kacmarcik, James Weatherall The current DOM Level 3

Re: Proposal to add USB keycodes to the current DOM3 key events

On Fri, Sep 7, 2012 at 11:44 AM, Travis Leithead travis.leith...@microsoft.com wrote: From: gary...@google.com [mailto:gary...@google.com] On Behalf Of Gary I've written up a brief proposal to enhance the current DOM Level 3 key events by adding USB keycodes. Nice. Yes, getting the keyboard