- From: fuchsia via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Jun 2018 14:32:23 +0000
- To: public-fxtf-archive@w3.org
I think my brain was trying to parse it as: <i>"{{DOMPoint}}, as well as <del>the</del> inheriting <ins>the</ins> interface {{DOMPointReadOnly}}, must be able to access and set the value of these variables."</i> But, on a slow read, after someone's pointed out what was intended and the import of the following paragraph has sunk in, the original makes sense.
At this point, I just want to close the request to save some embarrassment. But, it <em>is</em> a confusing chunk. So, quickly sketching, maybe that sentence should be folded into the next paragraph, and the distracting ref to DOMPoint dropped, so it reads:
> The value of these internal member variables may be set, as well as read. And an interface exposing a {{DOMPointReadOnly}} object as an attribute or returning a {{DOMPointReadOnly}} object from a function may be able to modify internal member variable values. Such an interface must specify this ability explicitly in prose.
--
GitHub Notification of comment by fuchsia
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/pull/291#issuecomment-395779498 using your GitHub account
Received on Friday, 8 June 2018 14:32:25 UTC