question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

loop initialization with new version of uploadcare 2.5.x

See original GitHub issue

After having upatated to latest version of uploadcare in my installation, 2.5X with jquery 2.1, I had a flickering effect. After investigating it I notice html element was like disapearing and reapearing. I put a watch on it and figure out that this function was being called repeteadly

uploadcare.namespace('', function(ns) {
    var cleanup, dataAttr, initialize, initializeWidget, selector;
    dataAttr = 'uploadcareWidget';
    selector = '[role~="uploadcare-uploader"]';
    ns.initialize = function(container) {
      if (container == null) {
        container = ':root';
      }
      return initialize($(container).find(selector));
    };

and called that function from jquery.sizzle

if ( newSelector ) {
    try {
      push.apply( results,
        newContext.querySelectorAll( newSelector )
      );
      return results;
    } catch(qsaError) {
    } finally {
      if ( !old ) {
        context.removeAttribute("id");
      }
    }

Uploadcare is not compatible with jquery 2.x branches ?

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:13 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
sinsunsancommented, Feb 1, 2017

It is 1 year and more that I posted this issue. On another project, I used latest version of uploadcare widget. Forget about that issue, and have little css debuging to do. So it does not disturbed me so much. But I noticed that I was unable to edit the css directly in chrome debug dev because of this annoying effect that refresh everything…

But I forget a bit about this issue, and thought it was another problem.

But in fact it was this very issue and it is 1 months ++ I am working with this annoying default because of uploadcare.

I suggest that you set UPLOADCARE_LIVE = false; by default, because many people probably are loosing time like me.

And it is a problem that is difficult to put a name on to search in google. Like a clear debug error message.

I do not know why it is not fixed in a more stable way now. @dmitry-mukhin

1reaction
Zmokicommented, Oct 10, 2017

Ok, thank you! We’ll update our docs soon. And with next major version of the widget we’ll change this behavior of the widget.

Read more comments on GitHub >

github_iconTop Results From Across the Web

File Uploader Initialization | Uploadcare Docs
This means that by default file uploaders are initialized during your page load. And, every ~100 ms we check if there are any...
Read more >
Docs File uploader - Uploadcare
Local attributes, initialized when a new File Uploader instance is created. The settings object. Global variables. Globals are specified as global JavaScript ...
Read more >
Uploadcare CDN - Docs
Uploadcare features a powerful CDN that can deliver your content across the world in no time. (Content Delivery Network is a system of...
Read more >
JavaScript API Documentation | Uploadcare Docs
This is for the version 2.x of the widget. ... Returns array of new initialized widgets, or empty array if no new instances...
Read more >
top5relatedtags - Stack Exchange Data Explorer
... 'keyboard-input', 'partial-postback', 'member-initialization', ... 'elasticsearch-x-pack', 'react-data-grid', 'webdriver-manager', ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found