[Geometry-1] TYPO: transposed DOMPointReadOnly and DOMPoint...

[fuchsia]

Typo: transposed DOMPointReadOnly and DOMPoint so the text matches the IDL. I think that's what was intended. (As with so much of this spec, the intent is opaque.)

[dirkschulze]

This sentence actually seems to be correct to me. DOMPoint inherits from DOMPointReadOnly.

[tabatkins]

Ah, I suppose what's unclear here is that the use of "inheriting interface" can be read as the opposite relationship ("the interface it's inheriting from") - "inherited interface" is the more usual form of the term.

[plehegar]

Marked as non substantive for IPR from ash-nazg.

[fuchsia]

I think my brain was trying to parse it as: "{{DOMPoint}}, as well as the inheriting the interface {{DOMPointReadOnly}}, must be able to access and set the value of these variables." 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 is 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.

[svgeesus]

So, is this "close, no edits needed"? Or are we waiting for edits for this small PR?

[dirkschulze]

@svgeesus I think the outcome is that the spec is correct but the spec text could be simplified (non-normative change).