Success! Looks like we've fixed this one. According to our records the fix was applied for TOUCH-4127 in a recent build.
  1. #1
    Sencha User
    Join Date
    Oct 2007
    Posts
    26
    Vote Rating
    0
    pgiraud is on a distinguished road

      0  

    Default Ext.Connection.upload first call raises javascript error

    Ext.Connection.upload first call raises javascript error


    REQUIRED INFORMATION


    Ext version tested:
    • Sencha Touch 2.1.1 GPL

    Browser versions tested against:
    • Chromium 25 (Ubuntu)

    DOCTYPE tested against:
    • HTML

    Description:
    • When calling Ext.Connection.upload, an error is raised the first time. Following calls work. Looking at the source code, it looks like the problem occurs when creating the iFrame and calling Ext::fly on the created Element.
    • May be a duplicate for http://www.sencha.com/forum/showthre...l=1#post945400

    Steps to reproduce the problem:
    • See test case code below.

    The result that occurs instead:
    The following error is raised.
    Code:
    Uncaught TypeError: Cannot set property 'ext-element-xxx' of undefined
    Test Case:
    Code:
        var frame = document.createElement('iframe');
        Ext.fly(frame).on('load', function() {alert('loaded');});

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    36,824
    Vote Rating
    836
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    This isn't a bug in Ext.Connection but Element not working with elements not in the DOM.

    Thanks for the report! I have opened a bug in our bug tracker.

  3. #3
    Sencha User
    Join Date
    Oct 2007
    Posts
    26
    Vote Rating
    0
    pgiraud is on a distinguished road

      0  

    Default


    Does the following message mean that the "Element not in DOM" bug has been fixed? Or does it mean that the bug described here has been mark as invalid?

    Success! Looks like we've fixed this one. According to our records the fix was applied for TOUCH-4127 in Sprint 31.
    Thanks a lot anyway.

Thread Participants: 1