Results 1 to 2 of 2

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

  1. #1
    Sencha User Animal's Avatar
    Join Date
    Mar 2007
    Location
    Bédoin/Redwood City
    Posts
    30,853
    Vote Rating
    87
      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
    Longtime Sencha engineer. Now surplus to requirements apparently...

  2. #2
    Sencha User evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    18,984
    Vote Rating
    933
      0  

    Default

    Thanks Nige, fixed in SVN.
    Twitter - @evantrimboli
    Former Sencha framework engineer, available for consulting.
    As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

Posting Permissions

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