Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134)

The getComputedStyle() design is very strange. My best guess for why it exists that way was that separate working groups produced the CSS APIs from the Node APIs, and they didn't want to collaborate and/or didn't have `partial interface` technology, so the CSS folks went with `getX(someY)` instead of `someY.getX()`.

I don't think there's anything special about promise return types that makes using them a cause for caution.

So I tend to agree that putting it as a method on `Node` makes more sense. It's a classic consistency vs. goodness tradeoff, in some sense. But in this case it's not a big pattern we're contemplating consistency consistent with---just a single weird old API from the early days of the web.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/134#issuecomment-436509411