Skip to content
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

IE11: Cannot redefine non-configurable property 'find' #60

Closed
sven5 opened this issue Jan 22, 2021 · 3 comments
Closed

IE11: Cannot redefine non-configurable property 'find' #60

sven5 opened this issue Jan 22, 2021 · 3 comments

Comments

@sven5
Copy link

sven5 commented Jan 22, 2021

With the current release 3.0.8 for .NET Core 3.1 I'm getting this error in IE11.

SCRIPT5078: Cannot redefine non-configurable property "find"
es.symbol.js (266,1)

Could help here?

Thanks

@sven5 sven5 changed the title IE11: Cannot refine non-configurable property 'find' IE11: Cannot redefine non-configurable property 'find' Jan 22, 2021
@Daddoon
Copy link
Owner

Daddoon commented Jan 22, 2021

Do you have a reproductive scenario for this error ?
I never encountered it in my tests.

This is maybe a bug in an older version of core-js bundled in this project, or a messy implementation of a third party polyfill.
Some hints here: zloirock/core-js#790

It would be interesting that i have a reproductive scenario, as i would also test on the last Blazor server versions in .NET 5.0.

I would then ship an update to for both .NET 3.x and .NET 5.0 if i find the issue.

@sven5
Copy link
Author

sven5 commented Jan 22, 2021

Hi @Daddoon

Thanks for your fast reply. I'm just investigating this issue and it seems that quill js is causing trouble here.

<script type="text/javascript" src="~/lib/quill/dist/quill.js"></script>

I registered quill before your polyfill lib and that seems to be wrong. When placing the quill reference after polyfill then it works.

@Daddoon
Copy link
Owner

Daddoon commented Jan 22, 2021

I think that quill.js may have it's own find polyfill internally, that is applied if the required find signature is not found.

Seems that there is some interactions between the two libs, i think one or the other (quill.js or the core-js part) does not react as expected while finding an existing signature.

What's happening here i think is that by placing your file after the blazor.polyfill lib make your quill.js lib not trying to implement the find signature, as it has been found previously.

Nothing blocking, i can close this i suppose !

@Daddoon Daddoon closed this as completed Jan 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants