Element#subNodes() major bug
-
MadRabbit
- did you put your element on the page before the
select?
- which browser is that?
- did you put your element on the page before the
select?
-
Douwe M.
1) What exactly do you mean?
2) This is Safari (so probably Chrome too), but looking at the code for Element#subNodes() it think it behaves like this in every browser (that you can count on, i.e. not IE). Haven't checked Firefox yet. -
Douwe M.
Fixed version, called
Element#subNodes2()(edited the line starting withreturn)Element.addMethods({
subNodes2: function(css_rule) { var first_child = this.firstChild; return first_child ? ((first_child.tagName && first_child.match(css_rule)) ? [$(first_child)] : [] ).concat(this.rCollect.call(first_child, 'nextSibling', css_rule)) : []; }, });</code>
-
MadRabbit
- Tag changed from bug, element#subnodes to bug, element
- State changed from new to resolved
pushed the fix on the server
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.