Taking the example from the test here..
RegExp.prototype.toLocaleString = "invalid";
[/r/].toLocaleString()
Currently,
Chrome : TypeError: string is not a function
Firefox: TypeError: (intermediate value).toLocaleString is not a function
Safari : TypeError: invalid is not a function (evaluating
'[/r/].toLocaleString()')
Another example:
i = 'invalid', window[i]();
Chrome : TypeError: undefined is not a function
Firefox: TypeError: window[i] is not a function
Safari : TypeError: undefined is not a function (evaluating 'window[i]()')
Example from http://crbug.com/406987
var foo; foo.bar.baz();
Chrome : TypeError: Cannot read property 'bar' of undefined
Firefox: TypeError: TypeError: foo is undefined
Safari : TypeError: TypeError: undefined is not an object
(evaluating 'foo.bar')
The developer's next step when getting a message like this 1) identifying
what
value is currently undefined and 2) backtracking to why.
For this CL we want to assist with this first step, so providing any context
about the original JS source would be most helpful.
So, is there any way to adapt the above work to include the original JS
source,
like what Safari has done?
https://codereview.chromium.org/861623002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
