Results 1 to 2 of 2

Thread: [2.x][FIXED] Invalid DomQuery(Xpath) selector used in Ext.Button

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Sencha - Ext JS Dev Team Animal's Avatar
    Join Date
    Mar 2007
    Location
    Notts/Redwood City
    Posts
    30,615
    Vote Rating
    54
      0  

    Default [2.x][FIXED] Invalid DomQuery(Xpath) selector used in Ext.Button

    Ext.Button contains

    Code:
        buttonSelector : "button:first",
    This is tolerated by DomQuery, and so works OK even though DomQuery is documented to require

    Code:
        buttonSelector : "button:first-child",
    But with the next generation of browsers including native DOM selection engines, this tolerance will disappear when DomQuery is upgraded to use native selection where available (Which must happen)

    See this thread: http://extjs.com/forum/showthread.php?t=45185

  2. #2
    Sencha - Ext JS Dev Team evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    18,606
    Vote Rating
    874
      0  

    Default

    Thanks Nige, fixed in SVN.
    Evan Trimboli
    Twitter - @evantrimboli

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •