[Proto-Scripty] Draggables mouse problem in an overflow-ed div

2009-03-21 Thread Gil
Hi everyone, I'm having some troubles with draggable images inside a div (overflow: auto; position: relative). If I scroll the div to drag an image in the newly displayed area, there's quite a gap between the mouse pointer and the image i'm dragging. I'm using a 2 column CSS design (that's to ex

[Proto-Scripty] Morph on Form Elements

2009-03-21 Thread Celso
How improve this? I need that my function call only elements of types "input type:text" and "select" function isSelected(obj){ if(obj.value != ""){ obj.morph('background:#ced9f9;'); }else{ obj.morph('background:#ff;'); } } function is

[Proto-Scripty] Re: $$ utility method returns href value instead of anchor tag reference

2009-03-21 Thread T.J. Crowder
Hi, > hmm, well, links[0] is returning a string, not the a object... No, it isn't. Richard already answered your question: Your alert coerces the object into a string, which implicitly calls the toString method on it, which (in the case of a link) returns the href. If you actually _try_ what

[Proto-Scripty] Re: Stopping events ..

2009-03-21 Thread T.J. Crowder
Hi, > Very strange but I'll take your word on it. > > Although I can't say I understand why the object wouldn't throw its > submit event after executing the submit method. Because by design, submitting a form programatically doesn't fire the onsubmit event. I think this is on the theory that if

[Proto-Scripty] Re: Stopping event propagation on a event handler added through onClick property

2009-03-21 Thread T.J. Crowder
Hi Jay, No problem. Yes, it was always function for me as well, but I was feeling paranoid. :-) -- T.J. On Mar 19, 8:30 pm, Jay wrote: > Thanks!!! T.J. that solved it. > Here is piece of code I have now: > > var DOM0Handler =  $(n).onclick; > $(n).onclick = ""; > n.observe('click', function(e

[Proto-Scripty] Re: Morph on Form Elements

2009-03-21 Thread T.J. Crowder
Hi, I'm not quite sure I understand the question, can you explain a bit more? If you mean you only want to call selecionado() for input type=text and select elements in your loop, replace this: var elem = $('formulario').elements; with this: var elem = $('formulario').select('input[ty

[Proto-Scripty] Re: IE8 compatibility

2009-03-21 Thread RobG
On Mar 20, 6:18 am, masterleep wrote: > OK, I found this particular one... if you call > input_elem.readAttribute('value'); > on an input element, and the value is equal to the empty string, then > in IE8 the result is null. Then that is a bug in IE 8. readAttribute uses getAttribute, which r

[Proto-Scripty] Re: IE8 compatibility

2009-03-21 Thread T.J. Crowder
@masterleep: I think there are still some IE8 issues. Now that a final is out, they'll probably get resolved soon. I know kangax (at least) is working on some of them and several have already been resolved in the trunk version. Would you give the trunk version a go? @RobG: > Then that is a b

[Proto-Scripty] Re: IE8 compatibility

2009-03-21 Thread Completely Free Dating - Andrew
Hi All, This appears to be a bug in IE, not prototype, as it is not applying the class attribute using the specified 'className' property (http:// msdn.microsoft.com/en-us/library/ms533560(VS.85).aspx), but using the attribute name 'class' instead, so as a work around I have added this around lin

[Proto-Scripty] Re: IE8 compatibility

2009-03-21 Thread kangax
On Mar 21, 10:16 pm, Completely Free Dating - Andrew wrote: > Hi All, > > This appears to be a bug in IE, not prototype, as it is not applying > the class attribute using the specified 'className' property (http:// > msdn.microsoft.com/en-us/library/ms533560(VS.85).aspx), but using the > attribut