+1 to device-independent events (di-events...hopefully not become die-events per the time perspective conversation) * katie * Katie Haritos-Shea Senior Accessibility SME (WCAG/Section 508/ADA/AODA) Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545 -----Original Message----- From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru] Sent: Friday, December 12, 2014 9:36 AM To: Simon Pieters; Arthur Barstow; Tobie Langel Cc: Ben Peters; public-editing-tf; public-webapps@w3.org; public-indie-ui@w3.org; public-html@w3.org Subject: Re: [editing] Responsive Input Terminology sounds quite reasonable to me. 12.12.2014, 16:41, "Simon Pieters" <simonp@opera.com>: > On Fri, 12 Dec 2014 13:39:47 +0100, Tobie Langel > <tobie.langel@gmail.com> > wrote: >> On Fri, Dec 12, 2014 at 1:00 PM, Arthur Barstow >> <art.barstow@gmail.com> >> wrote: >>> What is your counter-proposal? >> Heh. >> >> Fair enough, I guess. :) >> >> These seem related to what Java calls semantic events [JAVADOC], so >> I'd >> give that a try to see if it fits the model. If not, would "abstract >> events" or simply "high-level events" work? Sorry if these have >> already >> been discussed and dismissed (haven't had much time to look through >> the >> archives, tbh). > > How about "device-independent events"? > > -- > Simon Pieters > Opera Software -- Charles McCathie Nevile - web standards - CTO Office, Yandex chaals@yandex-team.ru - - - Find more at http://yandex.comReceived on Friday, 12 December 2014 15:51:59 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:32 UTC