<marcosc> Meeting structure https://github.com/w3c/webappswg/issues/10
<tink> `present+ LĂ©onie (tink)
<tink> Code of conduct: https://www.w3.org/Consortium/cepc/cepc-20141022/Overview.html
present
<asa_> present
<garykac> +garykac
<Yves> code of conduct: https://www.w3.org/Consortium/cepc/cepc-20151007/
<Yves> webapps charter: https://www.w3.org/2019/05/webapps-charter.html
<tink> https://www.w3.org/Consortium/cepc/cepc-20141022/Overview.html
<marcosc> https://github.com/w3c/webappswg/issues/10
<marcosc> Mek: not much progress, but we added new promisy methods. Don't expect to see many more changes but we need cleanup
<marcosc> https://github.com/w3c/FileAPI/issues/138
<marcosc> Mek: some mostly need to talk to annevk
<marcosc> MC: anything blocking?
<marcosc> Mek: just time
<marcosc> Let's move onto Gamepad API
<marcosc> https://github.com/w3c/gamepad/issues/99
<marcosc> steve: we are trying to get to CR. We have a privacy issue and a proposal.
<marcosc> steve: we have some tests in WPT.
<marcosc> MC: it would good to see how much test coverage we have .
<marcosc> Indexed Database API
IndexDB
<marcosc> https://github.com/w3c/IndexedDB/issues/290
dmurph: three major changes
... 1) IDBFactory databases
2) IDBTransaction commit() -- explicit transaction commit
dmurph: 3) IDBCursor request
attribute (?)
... Better controls over transaction lifetime and status
... Maybe not enough support to move to CR due to lack of
adoption
... Need to chat with Mozilla people
... Seeking opinions from Apple; Brady/Apple is the person, but
not present
<Yves> https://github.com/w3c/IntersectionObserver/issues/380
IntersectionObserver tl;dr -- basically ready for CR, implemented in all major browsers
szager evangelizing for IntersectionObserver V2 (occlusion detection)
PointerLock
Issues due to OS display scaling affecting cursor location
There's a path forward on Windows, looking for Apple people to collaborate
Looking for usability feedback prior to CR
Push API
Concern about testability
Improvements in interop over last 12 months
Editor(s) unsure whether it's worthwhile to move to CR
API may undergo additional churn, so CR may be premature
Screen Orientation API
Spec overhauled over last 12 months
Added lots of WPT
Testing on mobile is tedious
Fun issues around lock() reentry
Still lots of work to do
Seeking input from WebKIt
Web Manifest spec
Limited progress; wanting for feedback from browsers
Testing the feature is hard
<aarongu> Shout out to Maximiliano Firtman (@firt)
Just got into Firefox preview, waiting for issues/feedback
concerns around BeforeInstallPrompt()
aarongu: Want to add "shortcuts"
to manifest, to enable long-press type shortcuts for
install
... Initial feedback is positive, more discussion necessary
<aarongu> shortcuts = context menu like capability
Web Share API
<aarongu> shortcuts background/discussion https://github.com/w3c/manifest/issues/582
This is an example of the standards process working well
shipped in chromium and webkit, being implemented in firefox
CR process should be smooth sailing
Do we want to support sharing files? Security concerns.
How to do feature detection for level-2 features?
Here come the editing specs..
UIEvents
Long crufty history of this spec
???: Need significant rewrites of old spec prior to CR
Anybody: who is the speaker?
garykac: This is grungy unglamorous work, but the current state is limiting other API's
Clipboard API
<garykac> hello
garykac: implemented text and
image support, spec work to follow
... Long list of desired features
... Async text clipboard API was first step; step two adds
image support
... Seeking feedback
jsbell will talk about IndexDB cursor requests
jsbell: cursor->request
bookkeeping was hard, now it's easy
... \o/
Input Events API
<garykac> Johannes Wil,
<garykac> Wilm
<marcosc_> jw
Johannes Will: Two levels of API
Level 1 implemented in chromium and WK
Level 2 only in @K
WK
Seeking feedback from chromium
<xiaoqian> Input Events and Contenteditable https://github.com/w3c/editing/issues/199
marcosc_: Maybe time to revisit two-implementor policy for spec progress
Johanness Will (JW): Level 2 was original proposal, but chromium discovered problems and backed off original proposal, leading to schism
JW: Onus on chromium to suggest path forward
Selection API
Postpone Selection API pending rniwa
ContentEditable
JW: All browsers have legacy
implementations without formal spec
... Intention is to revisit after Input Events API
... execCommand is buggiest part
<jsbell> IDBCursor request video: https://www.youtube.com/watch?v=y1TEPQz02iU
jsbell: Please subscribe to my YT channel!
<jsbell> Pthbbbbt
Accessibility specs...
Editors not present, can anyone speak?
Leonie Watson (LW): Lack of tests is primary impediment
LW: Extracting old accessibility
from HTML5 spec created lack of implementors
... There are active participants from Apple and Mozilla
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/tantek/???/ Present: (ETRI) (Google) (Igalia) Ahmed Brufau Kangchan Laszlo_Gombos Lee Mek Mike_Wasserman Mustaq NavidZ Olli_Pettay Oriol SteveBecker Yves aarongu bkardell_ cmp dlibby ella jungkees marcosc wanderview xiaoqian Daniel Murphy christianliebel heejin hober Dongwoo garykac ricea annevk beverloo sagoston GameMaker kelvin Darwin_Huang oyiptong Dan Appelquist tantek whsieh grisha sanketj jsbell wonsuk___ joemedley Victor Costan No ScribeNick specified. Guessing ScribeNick: szager Inferring Scribes: szager Agenda: https://github.com/w3c/webappswg/issues/10 WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]