--mangle-props mangles the "pan" property of an AudioContext stereoPannerNode

[jameswilddev]

Bug report or feature request?
Hello! I've found that the "pan" property of an AudioContext stereoPannerNode gets mangled by the --mangle-props argument.

ES5 or ES6+ input?
ES3

Uglify version (uglifyjs -V)
uglify-js 3.1.3

JavaScript input
var context = new AudioContext()
context.createStereoPanner().pan.linearRampToValueAtTime(1, context.currentTime + 3)

The uglifyjs CLI command executed or minify() options used.
'var context = new AudioContext(); context.createStereoPanner().pan.linearRampToValueAtTime(1, context.currentTime + 3)' | uglifyjs --compress --mangle --mangle-props

JavaScript output or error produced.
var context=new AudioContext;context.createStereoPanner().t.linearRampToValueAtTime(1,context.currentTime+3);

Thanks!

[kzc]

So just to be clear, you'd like the following change?

--- a/tools/domprops.json
+++ b/tools/domprops.json
@@ -4395,6 +4395,7 @@
     "paintRequests",
     "paintType",
     "palette",
+    "pan",
     "panningModel",
     "parent",
     "parentElement",

@alexlamsl Should the dom properties be updated with other recent browser changes?

[alexlamsl]

@kzc personally I wouldn't care if the whole Oxford Dictionary is loaded into tools/domprops.json 😏

Jokes aside, if anyone have a need for these changes please come up with a PR - a simple test case under test/compress/ should cover it nicely.

[kzc]

@alexlamsl What I meant was to open tools/props.html in the latest versions of the major browsers to see what new DOM props it comes up with. It would beat doing it manually/piecemeal.

[jameswilddev]

Just taking a look at that tools/props.html file; I've got quite a few browsers here I can test it on:

• IE8
• IE9
• IE10
• IE11
• EdgeHTML 15
• Chrome 61.0.3163.100 (win64 and Android)
• Firefox 56.0 (win64 and Android)
• Windows Phone 7.8
• Nintendo 2DS Browser
• Safari (iOS 11.0.1)

However, due to the use of Object.getOwnPropertyNames and .foreach it doesn't run on many of these platforms. I'll see about making it ES3-safe.

[jameswilddev]

Yeah that isn't as trivial as it looks from my armchair ivory tower :)

[alexlamsl]

for (var key in obj) { … } should be able to replace Object.getOwnPropertyNames() in this case.

Failing that, I'll have a poke at that HTML on IE8 this weekend.

[jameswilddev]

You'd think so but there's complexities; for (var key in obj) doesn't work for arrays under IE8 for example. I might take another look at the weekend, I think I'm a bit drained tonight. Cheers for looking!