Thank you for your response, i will do that
On Oct 1, 10:57 pm, kangax <[EMAIL PROTECTED]> wrote:
> On Sep 30, 10:51 am, "[EMAIL PROTECTED]"
>
>
>
>
>
> <[EMAIL PROTECTED]> wrote:
> > Hi,
>
> > i have a Problem, i Code at a WYSWYG Editor, with Sortables. Now The
> > Porblem is that in FireFox 3 i
Yeah. could be, though I need to somehow get around it.
anyways, your example didn't work, and resultet in the same.
On 1 Okt., 20:36, Diodeus <[EMAIL PROTECTED]> wrote:
> It looks like something about your negative margin is messing things
> up.
>
> Try something like this instead:
>
> new Effec
This exact question was asked today at TAE.
At this time, no. stopObserving will not go through the children of
the container and remove events. In the future it is certainly
possible. Mind you it wouldn't be very difficult to write your own
method to recurse through all the children of a give
Hi,
Incase I've missed it, does prototype keep documentation in a raw
format (ie XML), or is the closest thing that the Atom feeds at
prototypejs.org/api
Brendan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Pro
Because the returned HTML includes JS code, IE gives me an error on
line 395 in prototype.js, and this is the evalScript function. After
searching on the Internet I discovered that others have this problem
also. Try a google search with the following text: "evalScript IE bug"
or "prototype evalScr
Hello,
if got the following problem,
if you go to http://www.webcustoms.nl/zend_wcustoms/ then the menu
will appear and dissappear again, if i go with my mouse over the home
button again,. nothing happens.
My JS code
:
document.observe('dom:loaded',
function()
{
dropdown = function(name)
Yeah. I know. I did that:
Element.addMethods({
clearEvents: function(element) {
element.descendants().each(
function(obj){
if (obj._prototypeEventID) {
obj.stopObserving();
}
}
);
element.stopOb
Try chaning your style to position:absolute.
On Oct 2, 3:46 am, revivedk <[EMAIL PROTECTED]> wrote:
> Yeah. could be, though I need to somehow get around it.
> anyways, your example didn't work, and resultet in the same.
>
> On 1 Okt., 20:36, Diodeus <[EMAIL PROTECTED]> wrote:
>
> > It looks like
I'm guessing that morph has a hard time transitioning from 50% to
137px. Perhaps it doesn't know what 50% is, if that's the case it
probably transitions from 0px to 137px instead, and you see things out
of screen for a while. I'm not sure if morph handles % to px, maybe
it's something that can be
Hi puckpuck!,
That's a really handy little snippet, so much simpler than manually
enumerating nested HTML elements and stopping them individually (which
I have previously done).
If this functionality were to be bundled within the Prototype
framework I personally think it would be better to offer
$('menu_home').observe('mouseover', dropdown('submenu_home'));
$('menu_home').observe('mouseout', dropdown('submenu_home'));
These 2 lines are your offensive lines of code. Try this instead:
$('menu_home').observe('mouseover',
dropdown.curry('submenu_home'));
$('menu_home').obse
When I made that post, I was very groggy, and realized I used a CSS
selector *, which well... is horrid slow, especially on IE. using
elem.descendants() instead would of made far more sense.
Also I would stay away from checking on the existing of
_prototypeEventID on the element. This is an int
Ok, it works now thanks =)
now i need to get some bugs out of it,
someone here who knowns how to get it out?
if i go over the home button the menu shows, but when im going into my
menu to click on a link my menu closes :S
On 2 okt, 15:07, puckpuck <[EMAIL PROTECTED]> wrote:
> $('menu_home').
Hi all,
I want to create a watermarked textbox (show text in the textbox that
when clicked dissapears). I want to use this to this to indicate that
one textbox is used forlogin and the other for password.
Someone has experience with this?
Thanks
Stijn
--~--~-~--~~~-
Thanks guys, I caught this:
"While it is not possible to directly query websites for data due to
the same origin policy, the tag does not honor the same-
origin policy and can be used in conjunction with JSON."
I'm assuming prototype is enforcing the same-origin policy then?
Thanks,
Dave
On O
Yeah, but if you firebug the Event object after recursive unregister, you
will see that every element that doesnt had a _prototypeEventID will create
an entry in Event.cache. This is because the way the eventId is generated
and THERE I'll not mess with :)
Those entry are empty, I know, but ohhh..
Event.observe(window, 'load', function() {
Event.observe('textbox_id', 'click', hideTxt);
});
function hideTxt(){
$('textbox_id').value='';
}
Is something like this you are referring to?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Prototype is not enforcing it, the browser is. Prototype provides a
wrapper for the XMLHTTP request, as do other Ajax libraries.
On Oct 2, 9:55 am, Dave <[EMAIL PROTECTED]> wrote:
> Thanks guys, I caught this:
>
> "While it is not possible to directly query websites for data due to
> the same ori
You can add another tag to your document, and point it to a
remote source other then your own domain, but that is not part of the
AJAX functionality provided in most libraries, including Prototype.
You would have to add a new