Hybrid View

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTGWT-2601 in 3.1.
  1. #1
    Sencha Premium Member
    Join Date
    Nov 2012
    Posts
    1
    Vote Rating
    0
    Jeff Raab is on a distinguished road

      0  

    Default GXT 3.0.1/3.0.2b - DomQuery.select bug?

    GXT 3.0.1/3.0.2b - DomQuery.select bug?


    A GWTTestCase with this code will pass using GXT 3.0.0 but fails in 3.0.1 and 3.0.2b. DomQuery.select doesn't seem to work anymore with class name selectors. Any ideas?

    Code:
            
    DivElement div = Document.get().createDivElement();
    div.setId( "test-id" );
    div.setClassName( "test-class" );
    
    BodyElement body = Document.get().getBody();
    body.appendChild( div );
    
    NodeList<Element> elements = DomQuery.select( "div" );
    assertEquals( 1, elements.getLength() );
    assertEquals( "test-id", elements.getItem( 0 ).getId() );
    assertEquals( "test-class", elements.getItem( 0 ).getClassName() );
    
    elements = DomQuery.select( ".test-class" );
    assertEquals( 1, elements.getLength() );
    assertEquals( "test-id", elements.getItem( 0 ).getId() );
    assertEquals( "test-class", elements.getItem( 0 ).getClassName() );

  2. #2
    Sencha User
    Join Date
    Sep 2007
    Posts
    13,971
    Vote Rating
    132
    sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light

      0  

    Default


    I moved this thread into the bugs forum and pushed it to the tracker so we can look into it. Thanks

Thread Participants: 1

Tags for this Thread