Meeting minutes
scribe BoCupp
jitsi or continue on Google Meet?
https://
<Travis> github: https://
johanneswilm: switch to Jitsi
BoCupp: also say we switch
resolved we will move to Jitsi
Anything futher on insertFrom... deleteBy.. etc.?
<Travis> github: https://
<Travis> BoCupp: Are we still exploring other options?
johanneswilm: Actually... we're on 122 w3c/input-events
… is there consensus on this?
BoCupp: Last status... on 12/10 we were asking DavidMulder...
johanneswilm: So, you and masayuki are in agreement?
BoCupp: Yes, I think so.
johanneswilm: BoCupp could you please confirm that this is ready to merge?
BoCupp: looked like masayuki was answering david's question... I think earlier in the thread it looked like masayuki would be disappointed if chromium did add these...
… will double check, and post to the issue.
Better times for the meeting?
github: https://
BoCupp: I think we did move to the current time... don't think we're planning on moving to another time..?
… I'm not sure there was interest in having alternating times?
johanneswilm: masayuki noted he wasn't able to attend meetings through 2021... but perhaps that's changed?
ACTION: check back with Masayuki and see what his attendance may be like?
Concern for screen readers
github: https://
BoCupp: Noticed my action here...
… checking with anupam...
snianu: No conclusion yet... perhaps we can discuss today?
BoCupp: Haven't had any progress on this one. Will come back to it next month.
Arbitrary clipboard types
github: https://
BoCupp: from our last meeting, it sounds like we are flexible and willing to adopt AnneVK's proposal.
AnneVK is OK with his own proposal..
Microsoft is OK with it.
whsieh: Would like a bit more time to think about it... do like the shape of this proposal more than the unsanitized flag, though.
… I'll give it some thought and post something here on this issue in about a week.
… was there some other issue that went into more detail?
… I was thinking of #150
… (https://
BoCupp: I think AnneVK split these into two issues... one was about the shape of the API (letting the author pick something from the clipboard)
<BoCupp> https://
BoCupp: the other about aligning between getData (datatransfer) and behavior of async API.
… so user agents may optional transfer that content.
whsieh: I'll leave a comment by next week.
ACTION: whsieh to leave a comment on https://
Checking on the blocked clipboard-write permission?
github: https://
BoCupp: I think the interested party is not here though...
… should probabaly ping Mozilla.
… Problem: we use clipboard read/write permission so that they can be granted to iframes.
… iframe's can't even do it without delegated authority.
… Office programs are hosted in different hosts and run in iframes. So we wanted to remove this.
… the objection was that firefox/safari were aligned on not wanting that.
… Seems like Apple has a trusted UI context menu. A second click is needed.
… Firefox has not shipped the API yet... I was wondering what Firefox' model is/will be. How would they solve the delegated authority issue?
… Will the adopt the Apple approach? Will the not have a permission? Have they even faced the issue yet?
… want to leave the issue as-is in hope of getting alignment on the current behavior? That's why we've left it blocked.
johanneswilm: Remind us why you need an iframe?
BoCupp: Yes, Microsoft Sharepoint is a shell that allows browsing of documents... when a doc is opened, Sharepoint loads a cross-origin iframe with the "word" logic to display it.
… Office app architecture is designed to be hosted in cross-origin iframes.
… Also, navigator.clipboard.read does not need to happen in context of a paste event. It may require a user gesture.
… We don't want the user to get prompted from some random iframe unless that authority has been delegated.
Travis: user only sees the address bar url.. iframe prompt would look like it came from that url. Confusing to the user.
BoCupp: I don't think there's an action to take today other than a followup later.
TPAC this year is in Vancouver, B.C.
BoCupp: I assume we'll want to meet at TPAC?
johanneswilm: Yes. We get extra participation (especially Google and Firefox).
… We also get participation from those who work on websites, which is great.
… Also other editors (CKEditor, etc.) which is very good input.
Travis: shall we reach out to W3C member companies who are also editors?
johanneswilm: We can get in some of the small players as Invited Experts.
… I can try to reach out to some of the non-big players. Folks like Faceboook may not be aware of these meetings and would have valuable feedback.
… I think it makes sense for you (big companies) to reach out...
… TPAC is week of Sept. 12
BoCupp: If Microsoft is not in Stage 6, we won't be able to attend big gatherings.
… I anticipate that the "Stage 6" is coming.
johanneswilm: You can reach out to editor folks at Microsoft?
BoCupp: Yes, monaco editor, rooster (?) editor.
johanneswilm: Same with you whsieh ?
whsieh: Yep, will do.
johanneswilm: Meeting adjurned (early!)
rrsagent: make the logs public
Yes, I know you are logging...
rrsagent: make logs public
rrsagent: draft the minutes