We just discovered what appears to be a very strange bug that appeared
with 1.6.1_rc2 (I don't have anything between 1.6.0 and 1.6.1_rc2 to
test.) When viewing the properties of the page, the several of the
properties are undefined and it crashes the browser.
Size: bytes (no number, just says byt
was an RC3, and
> now the final[1] is out.
>
> [1]http://prototypejs.org/download
> --
> T.J. Crowder
> tj / crowder software / comwww.crowdersoftware.com
>
> On Oct 1, 2:51 pm, laurin1 wrote:
>
>
>
> > We just discovered what appears to be a very strange
Hmm, so, I guess we are the only ones having this problem?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups
Has anyone tested Prototype with 8 Beta 2? I just started and I am
getting some error right off the bat. Not positive they are Prototype
related, but could be
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prot
So when does it become a high priority?
On Oct 23, 5:44 pm, kangax <[EMAIL PROTECTED]> wrote:
> On Oct 23, 1:59 pm, laurin1 <[EMAIL PROTECTED]> wrote:
>
> > Has anyone tested Prototype with 8 Beta 2? I just started and I am
> > getting some error right off
Apparently, this does not work? I get this error message when I try
it:
uncaught exception TypeError: Object # has no method 'each'
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
It works fine on arrays, if that is what you are asking.
On Nov 14, 2:39 pm, "Alex Mcauley" <[EMAIL PROTECTED]>
wrote:
> each does an array itterator no ?
>
>
>
> - Original Message -
> From: "laurin1" <[EMAIL PROTECTED]>
> To: "
I'm sorry. My brain is fried, it works on arrays with simple values,
but not arrays with Objects IN them. Mispoke.
For instance, in IE and in Chrome, this works fine:
$a = new Object();
$a['testme1'] = 'tested1';
$a['testme2'] = 'tested2';
$a['testme3'] = 'tested
Like I said, this code works just fine in IE, but in Chrome, it does
not work.
>$aEle = $('TicketOptions').getElementsByClassName('LoadChecks');
>$aEle.each(function($s){
>if($s != $sEle) $s.checked = false;
>});
No error in the browser, but the JS debugg
; });
>
> 1
> 2
> 3
> 4
> 5
>
> will only observe the last element with classname=someClass
>
> Regards
> Alex
>
> - Original Message -
> From: "laurin1" <[EMAIL PROTECTED]>
> To: "Prototype & script.aculo.us"
>
If on window.onload, I load
Event.observe($sEle, 'mouseover', HighlightElementOn2($sEle,
$sChangeText));
For some reason, the event onMouseOver is firing immediately, as the
text changes color on loading the page, rather than on mouseover. Can
someone help me understand what I am doing wrong?
--
Ok, I know why that is happening, it's because I passed the function
as HighlightElementOn2($sEle, $sChangeText), instead of
HighlightElementOn2. So the question is, how do I pass arguments via
observe?
On Nov 26, 11:04 am, laurin1 <[EMAIL PROTECTED]> wrote:
> If on window.
So, why can't your scripts be in the head? Do you know you can add
scripts to the head dynamically? Like this:
var fileref = document.createElement('script');
fileref.setAttribute("type","text/javascript");
fileref.setAttribute("src", '/javascript/common20.js');
if (typeof fileref != "undefined"
var $aCSS = document.getElementsByTagName('style');
$aCSS.each(function($sEle){
alert('test');
});
I can make this work with $$, and if I use
document.getElementsByTagName('style')[0], I can access each one
individually. So why can't I use each()?
--~--~-~--~~~-
I was under the impression that $$ was not very efficient, or do you
mean there is another way that I am overlooking?
On Dec 1, 3:25 pm, Jarkko Laine <[EMAIL PROTECTED]> wrote:
> On 1.12.2008, at 23.14, laurin1 wrote:
>
>
>
> > var $aCSS = document.getElementsByTagName(&#
Why does Prototype through and error when trying to disable an img? It
says that object does not support property or method. However, I can
enable and disable the img element via HTML without a problem.
--~--~-~--~~~---~--~~
You received this message because you are
This is the same problem I had before up to 1603, and I fixed it with
help of this forum (http://groups.google.com/group/prototype-
scriptaculous/browse_thread/thread/a1c745463251a95d/47692ec72bb65c5b?
hl=en&lnk=gst&q=__onDOMContentLoaded#47692ec72bb65c5b),
by adding nothing.js to line 4124, as s
Never mind. This problem is caused by TinyMCR and IE7.
On May 1, 3:35 pm, laurin1 wrote:
> This is the same problem I had before up to 1603, and I fixed it with
> help of this forum (http://groups.google.com/group/prototype-
> scriptaculous/browse_thread/thread/a1c745463251a95d/47692ec
18 matches
Mail list logo
