|
Yeah, that’s what I assumed. I was
digging into it because I was having an IE problem and got confused by the duplicate.
It turned out that I was calling the clone
too early – IE wasn’t setting the position right because the page
wasn’t finished rendering. So I changed the clone call to happen later
and it worked. rahul From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory Hill I noticed that as well; I think he just
forgot to delete the old one. Not sure, though. I believe your
assumption that the 2nd will override the first is correct, and
having used the function, the 2nd one is what is called by all of
the browsers I’ve tested. Greg From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rahul Bhargava Haven’t seen anyone ask about this yet… why are there 2 Position.clone() methods in
Prototype.js? It seems that the second would overwrite the first, and the
second has lots more options. Am I missing something? Thanks, rahul |
_______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
