Skip to content

chore: fix warning about unconfigurable property #9599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

devversion
Copy link
Member

Fixes that some browsers in Browserstack or Saucelabs warn about the defineProperty call in the interactivity checker tests.

LOG: 'Attempting to configure 'frameElement' with descriptor '{}' on object '[object Window]' and got error, giving up: TypeError: Attempting to change the getter of an unconfigurable property.'.

This happens because some browsers explicitly set all properties to configurable: false on window objects. To avoid such warnings, we can just check if the properties is configurable (or doesn't exist).

@devversion devversion requested a review from jelbourn as a code owner January 25, 2018 15:26
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 25, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 25, 2018
@devversion devversion force-pushed the chore/fix-warning-unconfiguraböle-property branch from 3ceab89 to 30aa9d6 Compare January 25, 2018 15:56
Fixes that some browsers in Browserstack or Saucelabs warn about the `defineProperty` call in the interactivity checker tests.

`LOG: 'Attempting to configure 'frameElement' with descriptor '{}' on object '[object Window]' and got error, giving up: TypeError: Attempting to change the getter of an unconfigurable property.'`.

This happens because some browsers explicitly set all properties to `configurable: false` on `window` objects. Since this is only happening inside of Safari, we don't overwrite the property.
@devversion devversion force-pushed the chore/fix-warning-unconfiguraböle-property branch from 30aa9d6 to 4573b49 Compare January 25, 2018 16:31
@jelbourn jelbourn merged commit 2f579b3 into angular:master Jan 25, 2018
@devversion devversion deleted the chore/fix-warning-unconfiguraböle-property branch January 25, 2018 20:43
@jelbourn jelbourn added target: patch This PR is targeted for the next patch release and removed target: patch This PR is targeted for the next patch release labels Jan 29, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants