W3C

– DRAFT –
(MEETING TITLE)

14 May 2021

Attendees

Present
BoCupp, comandeer, GameMaker, grisha, snianu, whsieh
Regrets
-
Chair
-
Scribe
grisha

Meeting minutes

https://meet.google.com/wry-qbtb-upy

https://github.com/w3c/editing/issues/278

<johanneswilm> +present present+

BoCupp: old issue that was tagged back in Feb

@johanneswilm yeah, we need to update the issue with the resolution

Action: update the issue wit the resolution.

https://github.com/w3c/editing/issues/305

grisha: Anupam been looking into pickling format implementation. Clipboard spec need to define mime types.

@BoCupp

@BoCupp: Mozilla also asked to define pickling formats. Defining custom formats would be hard. Is it reasonable to agree on a set of well-known formats?

@johanneswilm: what advantages will web devs have?

of having a well defined list

@BoCupp: having a guarantee will help developers to use formats that are interoperable.

johanneswilm: on some platforms, other formats are not supported at all. What do we do then?

@whsieh: would it be reasonable to define what is already supported?

grisha: should we define the name pattern of how browsers expose pickling formats?

@whsieh: Webkit offers a single blob with ability to paste multiple types there

@BoCupp: chromium does the same but we like FF approach where it lists all types on clipboard

@whsieh: we thought about providing an api but FF approach allows to implement delayed rendering

@whsieh: coco platform nspasteboard and uipaste board which I am not sure we have the support for it today.

@BoCupp: Does it enforce naming requirement?

@whsieh: not sure would need to check

@BoCupp: if there are particular uti that represent well known formats, we have to make sure they are not overtaken by pickling formats

@whsieh: +1 to last point

@BoCupp: I don't think we should block pickling on defining well-known formats.

@johanneswilm: +1 to that

@BoCupp: if we specify well known formats, should we specify sanitization as well?

@johanneswilm: if sanitization is different in browsers, it would be difficult for web developers. Citation managers add extra semantic info to make it work with libre and office. But the browser would strip it down.

@johanneswilm: academic word processor sees Google docs and handles it in particular way. Sees another structure and recognizes MS Word. But in cases where browser strips down unknown structures, webapp won't be able to handle the original content.

@whsieh: we built sanitizer for cases when Word was putting user personal information.

@whsieh: as long as the content is visible, it should be ok.

@BoCupp: that's for well-known formats. This will not be a case for pickling format.

<BoCupp> FYI for the Apple folks on the call, there is a request for position on clipboard pickling: https://lists.webkit.org/pipermail/webkit-dev/2021-May/031855.html

@johanneswilm: we collected enough votes for forming Editing WG. There were couple of organizations that wanted for lists, tables, image editing behaviors be specified in charter in order for them to support the proposal.

<johanneswilm> https://w3c.github.io/editing/charter-drafts/editing-2021.html

@BoCupp: WG participants should be on board with deliverables defined in the charter.

@BoCupp: call out any concerns.

Summary of action items

  1. update the issue wit the resolution.
Minutes manually created (not a transcript), formatted by scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).

Diagnostics

No scribenick or scribe found. Guessed: grisha

Maybe present: @BoCupp, @johanneswilm, @whsieh, johanneswilm