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

> The custom format map is an implementation detail. We don't expose it to the web.

From the web perspective, yes, the custom format map and the native types used are an implementation detail. Web sites don’t see those things. From the native app perspective, the custom format map and the native types used are not implementation details.

In a more general sense, when we write web specs, we want to be careful how we specify new DOM features and attributes, to make sure they fit in with other existing features. We want them to be elegant and straightforward, and as idiomatic-feeling as we can achieve. When we specify the native integration aspects of web specs, we want to take the same care in attempting to achieve the same goals. Native apps are going to be interacting with this spec just as much as web sites are going to be interacting with this spec. We should offer those native apps the most elegant, straightforward, and idiomatic spec as possible.

That’s why I want to clean this up now, while (AFAICT) there are no Mac apps yet using this feature.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/412#issuecomment-1341369598

You are receiving this because you are subscribed to this thread.

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