Re: [w3c/editing] The Web Custom formats specification does not appropriately use the macOS API (Issue #412)

> The second issue is the existence of a custom format map.

The custom format map is an implementation detail. We don't expose it to the web. It is only useful on platforms where the atom table could be exhausted by registering new clipboard formats. When the atom table is exhausted, the system goes into an irrecoverable state. To address this issue, we came up with the mapping idea so we can have a hard limit on how many formats you could write to the clipboard on those platforms.

> The custom format map is specified to have the format type com.web.custom.format.map, and the various formats are specified to have the format names com.web.custom.format[\d+]. This specification is not the work of [web.com](http://web.com/), and thus using the com.web.* prefix is inappropriate. If this is a W3C specification, a prefix of org.w3.* is probably the most appropriate.

@whsieh @annevk Thoughts?

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

Message ID: <w3c/editing/issues/412/1341345812@github.com>