Description of the problem

It seems lack of some properties in MeshPhysicalMaterial document.

https://threejs.org/docs/#api/en/materials/MeshPhysicalMaterial

Ever what I noticed are

• clearcoatNormalScale
• clearcoatNormalMap
• sheen
• transparency

We should update.

Three.js version

• Dev
• r113
• ...

Browser

• All of them
• [ ]

If a material has an existing prefiltered cubemap set, then updating the material's cubemap property material.cubeMap = cubemapAsset.resource will have no effect as this call doesn't update the prefiltered textures in the material.

Changing a material's cubemap should at least clear old cubemap data, and ideally update it to the new maps.

In section 3.4 (Feature Dependencies), you'll find tables describing the features and their dependencies in terms of user consent and feature policy.

In particular, there's the information in the screen capture I have included here:

The table says that local requires consent for

Community contribution added in #1125

Controls a transform scale on the built-in AR button only. Eventually this could be deprecated in favor of using a ::part.

We should expose values like the build version number, as well as what dpdb values are being used easily from WebVRPolyfill for debugging

Running the tabs default launch command (-t) does not respect redirects at the target.

$ node . -t https://aframe.io/a-painter

☝️ The above will error, even though the server will redirect to https://aframe.io/a-painter/ and serve HTML there:

$ curl -i https://aframe.io/a-painter
HTTP/1.1 301 Moved Permanently
Date: Mon, 03 Jun 2019 20:10:27 GMT
Content-Type: text/ht

It may save a few headaches to mention in either the README or on the pages themselves the secure context requirement for WebXR, needing either https or localhost/127.0.0.1, and how to go about that. Via immersive-web/webxr-samples#47

If a map has a floor anchor, it won't get used properly. If the user reset tracking, or the floor anchor gets deleted, things break.

webxr-2019 branch has been merged to master #75. But Readme looks still old, for example navigator.xr doesn't have requestDevice() method now. I'm happy if readme is updated.

You should be able to add text to a scene. Either as a Text Geometry or SDF text, probably both.

There's already a text component in AFrame that we can use in Hubs. We would need to add a new Spoke node with the ability to preview the text.

I think we should export the following properties:

value
align
anchor
baseline
color
he

Noticed the right half of the keyboard works correctly for transparency during hover, but the left side keys show a black background on hover. The keys circled below are the ones tested as having this issue.

![moonkeyboard](https://user-images.githubuserco

Ideally we will have a gltf for each device, but in the meantime we could use a generic VR input device like https://poly.google.com/view/cUT5C1Krx7g or https://poly.google.com/view/0n5B6e5lYZe

• blog post
• source code

downloads (APKs)

• public release: APKs are available from the 0.1 release, its [initial public release](https://blog.mozvr.com/firefox-reality-b

At the moment most of the source code is typed as any which is a start but not particularly useful. Some of the types might require some runtime inspection because they are coming from the vendorered artoolkit library.

Currently no asset validation is performed; this issue would enable at least walking the asset to ensure required nodes are present.

Description:

should not throw

Insufficient number of arguments or no entry found.
Alternatively, run 'webpack(-cli) --help' for usage info.

• A-Frame Version:
• Platform / Device:
• Reproducible Code Snippet or URL:

Exokit by default does not render back to the main canvas when already in XR mode.

We should probably make it a configuration option to mirror back to the page canvas, and otherwise put up a blocker that the XR session is in progress and you should put on your headset.