Re: [w3c/clipboard-apis] Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization (Issue #206)

RESOLUTION: *Document all the behaviors in a way that makes all browsers compliant with the spec. Use non-normative notes for browser specific quirks and options*

Minutes:
6:27 PM snianu: sanitization behavior is different in browsers
6:28 PM unsanitized would let authors to opt-out
6:29 PM dandclark: since the behavior varies already so much, seems reasonable
6:30 PM snianu: we've been asked to have unsanitized option
6:31 PM snianu: would like to have something in the spec which would be compatible with all the browsers
<smaug> edgar: Gecko probably won't implement that, since we want the align with the old API
6:32 PM but with enhanced privacy mode we could sanitize
<whsieh> FWIW, WebKit has the same stance as FF — same behavior as DT (which sanitizes in WK), so we won't support this optional property
<smaug> snianu: we'd like to have flexibility in browser implementations
6:35 PM whsieh: we want to align with our legacy API.
6:36 PM whsieh: this sounds reasonable, but we don't need option to let authors to know if sanitization is supported
— •dandclark "pleaseUnsanitizeIfYouWant"
<smaug> smaug: It is confusing if the property name hints about unsanitization  and that doesn't happen
<smaug> edgar: problem is the inconsistency with the legacy API
<smaug> whsieh: author shouldn't ever expect certain markup
6:43 PM snianu: want to make sure all the behaviors are documented
6:44 PM snianu: we can add non-normative note
6:45 PM johanneswilm: ...so that you cover web authors who are not on mac/safari
6:46 PM smaug: we're ok with this
6:46 PM whsieh: we as well

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/206#issuecomment-1858499460
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/clipboard-apis/issues/206/1858499460@github.com>