Skip to content

Conversation

toji
Copy link
Member

@toji toji commented Apr 12, 2019

Fixes #576. Specifies that the object returned by XRRigidTransform's
inverse attribute must always be the same JS object and, furthermore,
the inverse of a transform returned by inverse must be the
originating transform.

@toji toji added this to the May '19 Working Draft milestone Apr 12, 2019
@toji toji requested a review from NellWaliczek April 12, 2019 22:09
index.bs Outdated
@@ -987,7 +987,7 @@ The <dfn attribute for="XRRigidTransform">orientation</dfn> attribute is a quate

The <dfn attribute for="XRRigidTransform">matrix</dfn> attribute returns the transform described by the {{XRRigidTransform/position}} and {{XRRigidTransform/orientation}} attributes as a [=matrix=]. This attribute SHOULD be lazily evaluated.

The <dfn attribute for="XRRigidTransform">inverse</dfn> attribute returns a {{XRRigidTransform}} which, if applied to an object that had previously been transformed by the original {{XRRigidTransform}}, would undo the transform and return the object to it's initial pose. This attribute SHOULD be lazily evaluated.
The <dfn attribute for="XRRigidTransform">inverse</dfn> attribute returns a {{XRRigidTransform}} which, if applied to an object that had previously been transformed by the original {{XRRigidTransform}}, would undo the transform and return the object to it's initial pose. This attribute SHOULD be lazily evaluated. The {{XRRigidTransform}} returned by {{inverse}} MUST return the originating {{XRRigidTransform}} as it's {{inverse}}.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"its"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, fixed.

toji added 2 commits April 15, 2019 11:23
Fixes #576. Specifies that the object returned by `XRRigidTransform`'s
`inverse` attribute must always be the same JS object and, furthermore,
the `inverse` of a transform returned by `inverse` must be the
originating transform.
@toji toji force-pushed the inverse_same_object branch from 349a1ee to 1159b42 Compare April 15, 2019 18:25
@toji toji merged commit 9553f1c into master Apr 15, 2019
@toji toji deleted the inverse_same_object branch April 15, 2019 19:36
@AdaRoseCannon AdaRoseCannon added ed:spec Include in newsletter, spec change ed:explainer Include in newsletter, explainer change labels May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ed:explainer Include in newsletter, explainer change ed:spec Include in newsletter, spec change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should XRRigidTransform.inverse.inverse return the original object?
3 participants