[Prototype-core] Re: IE bug still there..
On 10/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
should be
4014: src='http://javascript:void(0)'\/script);
I forget what brings up the error but.. :) fix! #3
no :) there is no javascript and http at all.
this it the right way to work with https. (afaik)
it should be as dean wrote:
@MSIE.+win: {
init: function() {
this.base();
// Matthias Miller/Mark Wubben/Paul Sowden/Me
document.write(script id=__ready defer src=//:\/script);
document.all.__ready.onreadystatechange = function() {
if (this.readyState == complete) {
this.removeNode(); // tidy
DOMContentLoaded.fire();
}
};
}
},
source: http://base2.googlecode.com/svn/trunk/lib/src/base2-dom.js
best,
w
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---
[Prototype-core] Re: :not() selector bugs
Andrew Dupont wrote: Not being able to use the descendant combinator after a :not clause, however, is a bug. Wiktor, feel free to report it; I'll try to fix it before 1.6 final. Thx Andrew! Here is the ticket with the attached diff: http://dev.rubyonrails.org/ticket/9696 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: $('my-element').$$('a[href=foo]');
On 8/30/07, Jeff Watkins [EMAIL PROTECTED] wrote: Oh come on. The syntax of this stuff is getting pretty opaque. Would it kill us to have method names that are self-documenting? Of course not. :) I agree with you and Mislav. If there is an standard Selectors API use those syntax, so I am ok with selectAllElements name. But because I use this $(foo).$$(.bar) syntax since months I get used to it. I don't think it's evil if we have a shortcut for selectAllElements and it is the obvious choice, the $$. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: $('my-element').$$('a[href=foo]');
On 8/30/07, Mislav Marohnić [EMAIL PROTECTED] wrote: I understand your need, and was also thinking of the same alias myself. But seeing how it looks like in real world made me give up on it. $ and $$ are OK in the front, but terrible in the middle of the chain. I respect your decision and of course I accept if it will not be aliased in the official version. In spite of this my favorite lib will be prototype, because - as I noted in the trac ticket - it's easy to extend so I can do it to myself. :) And thats the reason why prototype is great. ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
