You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started to notice this in Chrome's Elements inspector when it shows the tag kept updating infinity.
Once I set the breakpoint to monitor what is going on, it seems that the uploadcare widget kept using a Sizzle function to add and remove id from the html tag for some reason.
This all stopped if uploadcare widget (imported by either npm and the <script> method) is removed.
Seems like it is by design.
But with Google Chrome v61, the frequent update / flickering of makes it impossible to edit the DOM / CSS in developer tools (this is how I noticed about the id updates in the first place).
Editing DOM / CSS in developer tools of Safari and Firefox still seems fine.
I started to notice this in Chrome's Elements inspector when it shows the tag kept updating infinity.
Once I set the breakpoint to monitor what is going on, it seems that the uploadcare widget kept using a Sizzle function to add and remove id from the html tag for some reason.
This all stopped if uploadcare widget (imported by either npm and the <script> method) is removed.
Here is a video showing what I noticed.
Full video: http://d.bbi.io/Q6wiJl
The text was updated successfully, but these errors were encountered: