Re: [w3c/clipboard-apis] `ClipboardItem`: clarify mime parsing (Issue #242)

johanneswilm left a comment (w3c/clipboard-apis#242)

TPAC 2025:
> Rohan
Spaces in MIME types are alright, but not according to the spec. Amend the spec maybe?
Use case in Chromium: web custom types
Johannes
Browsers support it, we should either change the browsers or the spec
Are we sure this is happening for all browsers, who filed the spec?
Megan
Someone from Servo probably is trying to implement it
Smaug
Did the spec change after the implementation?
Rohan
No reason to not have the space
Johannes
Reasons to generally be restrictive. But given that they are currently allowed and there is some argument to use them, maybe they should be allowed.
Smaug
What is the use case of the constructor? From JS.
Rohan
write() uses this
Smaug
The easiest way to follow the spec
Megan
If no one follows the spec, we don’t know what will break
Johannes
Should we investigate between now and December
All
Yes, okay
Megan
It’s a bad situation overall, we don’t want this to be a blocker for implementing new web engines.


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

Message ID: <w3c/clipboard-apis/issues/242/3642432395@github.com>