123 0 false 2008-07-07T23:14:39+01:00 25555 2009-10-31T00:00:00+00:00 1634 203 element-getelementbyid-doesn-t-work-for-elements-not-in-document 325 2706 open defect regression selectors slick 2009-11-21T15:06:19+00:00 21395 Jan Kassens David Thomas Aylott http://mootools.lighthouseapp.com/projects/2706/tickets/203 2.0 This appears to be by design. Element.getElementById calls this.ownerDocument.getElementById to find elements... but what if I'm trying to find an element in an object not in the document (say something returned from AJAX)? It doesn't work. Element.getElement doesn't work either, because it calls Element.getElementById. In my mind at least this is a big usability bug. This appears to be by design. Element.getElementById calls this.ownerDocument.getElementById to find elements... but what if I'm trying to find an element in an object not in the document (say something returned from AJAX)? It doesn't work. Element.getElement doesn't work either, because it calls Element.getElementById. In my mind at least this is a big usability bug. <div><p> This appears to be by design. </p><p> Element.getElementById calls this.ownerDocument.getElementById to find elements... but what if I'm trying to find an element in an object not in the document (say something returned from AJAX)? It doesn't work. </p><p> Element.getElement doesn't work either, because it calls Element.getElementById. </p><p> In my mind at least this is a big usability bug. </p></div> 4325 0 This appears to be by design. Element.getElementById calls this.ownerDocument.getElementById to find elements... but what if I'm trying to find an element in an object not in the document (say something returned from AJAX)? It doesn't work. Element.getElement doesn't work either, because it calls Element.getElementById. Element.getElement at least used to work in this case in Mootools 1.1. In my mind at least this is a big usability bug. <div><p> This appears to be by design. </p><p> Element.getElementById calls this.ownerDocument.getElementById to find elements... but what if I'm trying to find an element in an object not in the document (say something returned from AJAX)? It doesn't work. </p><p> Element.getElement doesn't work either, because it calls Element.getElementById. Element.getElement at least used to work in this case in Mootools 1.1. </p><p> In my mind at least this is a big usability bug. </p></div> false 2008-07-07T23:17:50+01:00 25555 --- {} 1634 203 element-getelementbyid-doesn-t-work-for-elements-not-in-document 0 2706 new defect 2008-07-07T23:17:50+01:00 25555 David David Valerio http://mootools.lighthouseapp.com/projects/2706/tickets/203 2.0 4325 0 i think it didnt work in the old version in IE. i'm not sure if this one should be patched because of speed reasons. could be useful for ajax results though. <div><p> i think it didnt work in the old version in IE. </p><p> i'm not sure if this one should be patched because of speed reasons. could be useful for ajax results though. </p></div> true 2008-07-14T00:33:38+01:00 25555 --- :tag: defect :state: new 1634 203 element-getelementbyid-doesn-t-work-for-elements-not-in-document 0 2706 hold defect regression 2008-07-14T00:33:38+01:00 21395 Jan Kassens David Valerio http://mootools.lighthouseapp.com/projects/2706/tickets/203 2.0 4325 0 Maybe there could be a different method for doing this if the element isn't in the document? That way speed could be preserved for the "typical" use of searching for elements in document. <div><p> Maybe there could be a different method for doing this if the element isn't in the document? That way speed could be preserved for the "typical" use of searching for elements in document. </p></div> true 2008-07-14T08:30:49+01:00 25555 --- {} 1634 203 element-getelementbyid-doesn-t-work-for-elements-not-in-document 0 2706 hold defect regression 2008-07-14T08:30:49+01:00 25555 David David Valerio http://mootools.lighthouseapp.com/projects/2706/tickets/203 2.0 4325 0 I was bitten by this too as I was trying to mess around with an html ajax response. The workaround I am using is to put the ajax response into a hidden div in the document, and ask the document for the element by id. <div><p>I was bitten by this too as I was trying to mess around with an html ajax response. The workaround I am using is to put the ajax response into a hidden div in the document, and ask the document for the element by id.</p></div> true 2008-11-12T18:23:01+00:00 25555 --- {} 1634 203 element-getelementbyid-doesn-t-work-for-elements-not-in-document 0 2706 hold defect regression 2008-11-12T18:23:06+00:00 37263 MikeC David Valerio http://mootools.lighthouseapp.com/projects/2706/tickets/203 2.0 4325 0 not sure if this currently works in slick or not, but it should. I should add some specs to test for this. <div><p>not sure if this currently works in slick or not, but it should.</p> <p>I should add some specs to test for this.</p></div> false 2009-03-17T01:26:55+00:00 25555 --- :state: hold :tag: defect regression :title: Element.getElementById doesn't work for elements not in document 1634 203 element-getelementbyid-doesn-t-work-for-elements-not-in-document 0 2706 open defect regression selectors slick 2009-03-17T01:26:59+00:00 123 Thomas Aylott David Valerio http://mootools.lighthouseapp.com/projects/2706/tickets/203 2.0 123 0 Are there specs for this now with the mocks? <div><p>Are there specs for this now with the mocks?</p></div> false 2009-11-21T15:06:17+00:00 25555 --- :assigned_user: 4325 1634 203 element-getelementbyid-doesn-t-work-for-elements-not-in-document 0 2706 open defect regression selectors slick 2009-11-21T15:06:19+00:00 21395 Jan Kassens David Thomas Aylott http://mootools.lighthouseapp.com/projects/2706/tickets/203 2.0