Unexpected exception is cropping up in latest version (Uncaught TypeError: Invalid property descriptor. Cannot both specify accessors and a value or writable attribute, #<Object>)
Reported by
asegs...@gmail.com,
Jun 10 2016
|
|||||
Issue description
Chrome Version : 51.0.2704.84 m
URLs (if applicable) : N/A, Internal application
Other browsers tested: Firefox
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: N/A
Firefox: OK
IE: OK
What steps will reproduce the problem?
(1) Open attached test file
What is the expected result?
No Uncaught TypeError: Invalid property descriptor. Cannot both specify accessors and a value or writable attribute, #<Object> Exception
What happens instead?
The above exception
Please provide any additional information below. Attach a screenshot if
possible.
,
Jun 14 2016
Tested the same on mac,win8.1 chrome version 51.0.2704.84 - observed no error in the console Please find the screenshot Could you please recheck and update the thread.
,
Jun 14 2016
Here's the error I'm getting, Win 7 Pro. Also included a shot of firefox without the error. My co-worker is also started experiencing this issue after updating.
,
Jun 14 2016
Thank you for providing more feedback. Adding requester "tkonchada@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 20 2016
I can confirm this is still an issue for me in the latest version: 51.0.2704.103 m (Win 7 SP1 Pro) I can also confirm this WAS working on Version 50.0.2661.102 m. Broke in Version 51.0.2704.84 m
,
Jul 15 2016
Able to reproduce the issue on mac 10.11.5 win7 and Linux chrome version 51.0.2704.106 - uncaught type error displayed But this error is not shown in beta 52.0.2743.75 dev 53.0.2785.8 and canary 54.0.2797.0 asegstro@, Could you please switch to latest builds and update the thread with your observation. We are expecting next stable push in few weeks.
,
Jul 15 2016
The issue seems to be corrected in the latest beta (52.0.2743.75 beta-m)
,
Jul 22 2016
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by asegs...@gmail.com
, Jun 10 2016