[WebXR] Update WebXR WPT directory

[Sergio Villar Senin]

[WebXR] Update WebXR WPT directory

[Sergio Villar Senin]

Created attachment 406090 [details]
Patch

[Sergio Villar Senin]

Ping reviewers

[youenn fablet]

Comment on attachment 406090 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=406090&action=review

> Source/WebCore/Modules/webxr/WebXRInputSourceArray.cpp:41
> +}

Could be inline

> LayoutTests/imported/w3c/web-platform-tests/webxr/dom-overlay/ar_dom_overlay.https.html:139
> +    debug('got viewerSpace');

Is it expected logging?

> LayoutTests/imported/w3c/web-platform-tests/webxr/dom-overlay/ar_dom_overlay.https.html:206
> +      debug('got rAF 1');

Ditto.

[Sergio Villar Senin]

Comment on attachment 406090 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=406090&action=review

Thanks for the review!

>> Source/WebCore/Modules/webxr/WebXRInputSourceArray.cpp:41
>> +}
> 
> Could be inline

OK. I'll move it.

>> LayoutTests/imported/w3c/web-platform-tests/webxr/dom-overlay/ar_dom_overlay.https.html:139
>> +    debug('got viewerSpace');
> 
> Is it expected logging?

This come straight from upstream. In our case it does not matter much because the debug() call is only implemented by Chromium AFAIK. For the rest of engines is an empty implementation. But I agree that it's weird to upstream something with debug statements.

[Sergio Villar Senin]

Committed r265546: <https://trac.webkit.org/changeset/265546>

[Radar WebKit Bug Importer]

<rdar://problem/66899462>