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
• [ ]

At the very least it should have some basic guidelines such as add tests for new code changes. It should also make a mention that Scribbletune works in the browser via Tone.js as well as in the terminal, hence a new code change needs to be such that it ll work in both the places. If it cannot, then that should be mentioned with some reasoning so that we can plan for it's creation in a subsequent c

I was trying to look up the API for the DebugPanel so I could locate an option to decrease the text size. I'm developing a smaller resolution game and the elements of the panel overlap and are unreadable/unusable at these lower sizes. Upon opening the API and searching/clicking on the DebugPanel link, I'm routed to [http://melonjs.github.io/melonJS/docs/me.DebugPanel.html](http://melonjs.github.io

Wondering if you could provide a basic example on how to use this in a express app?

Demos in the landing page does not work well on mobile phone.

• Check the current status of each mobile platform/browsers on how to handle multichannel audio file.
• Test the demos with Daydream View.

I'm having a little bit of trouble reverse engineering the structure of a default plugin; i.e., which classes are held as instances of which classes, which classes are communicating, is IGraphics an instance contained within an IGEditorDelegate, how do the graphics editor delegate and the DSP "editor delegate" communicate, etc. My friends who have tried using IPlug generally have the same experien

#136 added customizable keys, but there is no way for users to discover this behaviour. Perhaps the text "Click to change" should be somewhere, perhaps as a tooltip?

Describe the bug
On at least one browser, the slice seams are visible.

To Reproduce
Steps to reproduce the behavior:

1. Go to Slice-9-Grid example
2. Observe seams as the scale changes

Expected behavior
They should not be visible, just like in Chrome

Screenshots
![Captura de Tela (218)](https://user-images