[Proto-Scripty] Draggable failing after first drag in Firefox?
Hi all,
I'm using:
Scriptaculous 1.8.2
Prototype 1.6.0.3
Firefox 3.0.15
I'm stumped with this one. Using the following code within the BODY
element:
div id=drag_demo_1 style=width:80px; height:80px; cursor:move;
background:#7baaed; border:1px solid #333;/div
script type=text/javascript
new Draggable('drag_demo_1');
/script
I'm finding that in Firefox, the div drags fine on the first effort,
but then upon the second effort, it remains stationary.
In IE8, the div drags every time I attempt to use it.
Aside from the standard HTML and calling the prototype scriptaculous
JS files, this is the only code on the page, and it still fails!
Stranger still, when I use FF to go to
http://wiki.github.com/madrobby/scriptaculous/draggable
and try the first draggable demo there, it works fine (though I am
unsure as to which version of Prototype Scriptaculous MadRobby is
using).
Has anyone seen this before? Can anybody comment?
All replies appreciated.
Thanks
WoolyG
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: Draggable failing after first drag in Firefox?
Hi WoolyG,
I'm sure that this code will work on FF 3.0.15.
Do you have any error in firebug?
You could try tpo dowload prototype 1.6.1 and scriptaculous 1.8.3 to
test if it's work ?
--
david
On 16 nov, 10:22, woolyg woo...@gmail.com wrote:
Hi all,
I'm using:
Scriptaculous 1.8.2
Prototype 1.6.0.3
Firefox 3.0.15
I'm stumped with this one. Using the following code within the BODY
element:
div id=drag_demo_1 style=width:80px; height:80px; cursor:move;
background:#7baaed; border:1px solid #333;/div
script type=text/javascript
new Draggable('drag_demo_1');
/script
I'm finding that in Firefox, the div drags fine on the first effort,
but then upon the second effort, it remains stationary.
In IE8, the div drags every time I attempt to use it.
Aside from the standard HTML and calling the prototype scriptaculous
JS files, this is the only code on the page, and it still fails!
Stranger still, when I use FF to go
tohttp://wiki.github.com/madrobby/scriptaculous/draggable
and try the first draggable demo there, it works fine (though I am
unsure as to which version of Prototype Scriptaculous MadRobby is
using).
Has anyone seen this before? Can anybody comment?
All replies appreciated.
Thanks
WoolyG
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: instanting and reinstanting a function: Ajax.PeriodicalUpdater
Hi Bill,
Isn't it just an Ajax.Request that you need, because the periodical
executer is used 'generally' without the need of a user click. I mean,
in your exemple, it's like you start at the begginning the periodical
updater, and after it reload every time there is new message the
target DIV.
But in your case, it seems that the call is done only once on a uxer
click. So just use AJAX.Request, and on click launch it. The only
think you will do is to manually update the div with the result of the
AJAX call.
--
david
On 15 nov, 15:36, bill will...@techservsys.com wrote:
When the user clicks a link it executes this function:
function fPendingMail() { //set the mail div to show
document.getElementById (maildiv).style.display = block;
new Ajax.PeriodicalUpdater('maildiv', 'mail/pending_mail.php',
{
method: 'get',
frequency: 60,
decay: 1
});
return false; //inhibit the href
}
and the maildiv appears and loads a list of pending mail messages and
all is good.
When they are done the script executes
document.getElementById (maildiv).style.display = none;
I know the div is still updating and I don't need it to so:
1) how do I stop the periodicalUpdater.
2) should I be de-instanting (whatver the correct verb is) the object
so that when the user clicks the link again it will not just keep
creating more instances of the Ajax.PeriodicalUpdater ?
bill
--
Bill Drescher
william {at} TechServSys {dot} com
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Ajax.Updater: alter retrieved content
Hello,
I use Ajax.Updater to update a div content.
I need to add scriptvarname = content/script to every content
retreived with Ajax.Updater. Is there a way to do it with Responders ?
I tried:
Ajax.Responders.register({
onSuccess: function(r) {
r.transport.responseText =
'test';
}
});
With no sucess.
Any idea?
Regards.
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: instanting and reinstanting a function: Ajax.PeriodicalUpdater
Bill.
You can assign the periodical to a variable and call stop on it if you wish
..
EG.
var myperiodical=new Ajax.Periodical..
myperiodical.stop(); // stops it ...
All this is defined but IMO unclear in the documentation
HTH
Alex Mcauley
http://www.thevacancymarket.com
- Original Message -
From: bill
To: prototype-scriptaculous@googlegroups.com
Sent: Monday, November 16, 2009 2:31 PM
Subject: [Proto-Scripty] Re: instanting and reinstanting a function:
Ajax.PeriodicalUpdater
david wrote:
Hi Bill,
Isn't it just an Ajax.Request that you need, because the periodical
executer is used 'generally' without the need of a user click. I mean,
in your exemple, it's like you start at the begginning the periodical
updater, and after it reload every time there is new message the
target DIV.
But in your case, it seems that the call is done only once on a uxer
click. So just use AJAX.Request, and on click launch it. The only
think you will do is to manually update the div with the result of the
AJAX call.
no, actually I want the div to be loaded when the user clicks, and reloaded
every minute it is visible.
--
david
On 15 nov, 15:36, bill will...@techservsys.com wrote:
When the user clicks a link it executes this function:
function fPendingMail() { //set the mail div to show
document.getElementById (maildiv).style.display = block;
new Ajax.PeriodicalUpdater('maildiv', 'mail/pending_mail.php',
{
method: 'get',
frequency: 60,
decay: 1
});
return false; //inhibit the href
}
and the maildiv appears and loads a list of pending mail messages and
all is good.
When they are done the script executes
document.getElementById (maildiv).style.display = none;
I know the div is still updating and I don't need it to so:
1) how do I stop the periodicalUpdater.
2) should I be de-instanting (whatver the correct verb is) the object
so that when the user clicks the link again it will not just keep
creating more instances of the Ajax.PeriodicalUpdater ?
bill
--
Bill Drescher
william {at} TechServSys {dot} com
--
Bill Drescher
william {at} TechServSys {dot} com
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: Ajax.Updater: alter retrieved content
You would have to modify the source as it does not push the object into the
onComplete callback...
Alex Mcauley
http://www.thevacancymarket.com
- Original Message -
From: Lox laurent.dincl...@gmail.com
To: Prototype script.aculo.us prototype-scriptaculous@googlegroups.com
Sent: Monday, November 16, 2009 12:36 PM
Subject: [Proto-Scripty] Ajax.Updater: alter retrieved content
Hello,
I use Ajax.Updater to update a div content.
I need to add scriptvarname = content/script to every content
retreived with Ajax.Updater. Is there a way to do it with Responders ?
I tried:
Ajax.Responders.register({
onSuccess: function(r) {
r.transport.responseText = 'test';
}
});
With no sucess.
Any idea?
Regards.
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Help Prototype in a few minutes per day
Hi all, As you know, the new API docs[1] are generated via PDoc[2][3] from the source code. Unfortunately, though, porting over the old docs[4] is a non-trivial process, just because of the volumes involved and because frankly the old docs were pretty out of date. (I cheerfully volunteered to do it -- I'm not Core, I just help out sometimes and help moderate the lists -- completely underestimating the size of the task; and then my Real Job got Real Busy and I'm just not going to get it done alone. In fact, I've done just about as much on it as I can.) Now YOU, in just a few minutes per day, can dramatically help Prototype's documentation by helping merge the old docs into the source (and updating them to be current as we go). There are a bunch of tickets in Lighthouse[5] related to merging the old docs in (that link will automatically search for them for you). The tickets have been divvied up into bite-sized chunks, so you can dip in and out quite easily, it's not a big commitment! Much of the work has already been done for you, by Tobie writing a script to reach into Mephisto (the CMS that handles the old API docs [and various other things]) and extracting the docs, automatically converting much of their markup into the new PDoc format. Those .pdoc files (which are just plain text) are attached to the tickets they relate to. So a lot of this is just copy-and-paste into the relevant source file. It's easy to get involved, especially if you're a Mac OS, Linux, or *nix user (but Windows users are welcome too!). Just: 1. Grab a copy of the the source: $ git clone git://github.com/sstephenson/prototype.git $ cd prototype 2. Build your local copy $ rake dist $ rake doc (You may need to install the bluecloth ruby-gem. If you find you need to install others, please post here so people know!) 3. Grab one of the merge old docs tickets[5] from Lighthouse 4. See if someone's already working on it (see the comments) and if not, add a comment saying you're working on it 5. Make your changes to the source. Please do take time to make sure that what you're doing is in keeping with the new PDoc formatting and such. 6. Check them by building your docs again (rake doc) 7. Build a patch: $ git add src/blah/blah.js (e.g., the file you modified) $ git commit -m doc: blah blah blah [#123 state:resolved] $ git format-patch origin (Note the doc: at the beginning of the commit line, and the [#123 state:resolved] at the end. The 123 should be the issue # of the issue you're fixing.) 8. Upload the patch file to the ticket. More info on getting the source and building patches and such on the Contribute page[6]. Some things to look out for in the docs: * Do the parameter names match the source? * Do the parameters have their types? * Are the examples correct? * Are the examples...overdone, overly chatty, or unrealistic -- e.g., in need of pruning? * Do all Examples headers use H5 (either by using an h5 element, or by using five has marks: #)? [1] http://api.prototypejs.org [2] http://pdoc.org [3] http://groups.google.com/group/pdoc [4] http://prototypejs.org/api [5] https://prototype.lighthouseapp.com/projects/8886-prototype/tickets?q=merge+old+docs+state%3Aopen+state%3Anewfilter= [6] http://prototypejs.org/contribute If we all pitch in a few minutes here and there, we'll get the new docs up-to-scratch in terms of information in no time! Many thanks in advance to anyone who pitches in. -- T.J. :-) --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Draggable failing after first drag in Firefox?
Hi David,
I'll do that and report back. Thanks!
On Nov 17, 1:13 am, david david.brill...@gmail.com wrote:
Hi WoolyG,
I'm sure that this code will work on FF 3.0.15.
Do you have any error in firebug?
You could try tpo dowload prototype 1.6.1 and scriptaculous 1.8.3 to
test if it's work ?
--
david
On 16 nov, 10:22, woolyg woo...@gmail.com wrote:
Hi all,
I'm using:
Scriptaculous 1.8.2
Prototype 1.6.0.3
Firefox 3.0.15
I'm stumped with this one. Using the following code within the BODY
element:
div id=drag_demo_1 style=width:80px; height:80px; cursor:move;
background:#7baaed; border:1px solid #333;/div
script type=text/javascript
new Draggable('drag_demo_1');
/script
I'm finding that in Firefox, the div drags fine on the first effort,
but then upon the second effort, it remains stationary.
In IE8, the div drags every time I attempt to use it.
Aside from the standard HTML and calling the prototype scriptaculous
JS files, this is the only code on the page, and it still fails!
Stranger still, when I use FF to go
tohttp://wiki.github.com/madrobby/scriptaculous/draggable
and try the first draggable demo there, it works fine (though I am
unsure as to which version of Prototype Scriptaculous MadRobby is
using).
Has anyone seen this before? Can anybody comment?
All replies appreciated.
Thanks
WoolyG- Hide quoted text -
- Show quoted text -
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Working Demo?
Before investing time and energy into implementing your auto complete addon I would like to see a working demo of it. The links I have found to your demo (http://demo.script.aculo.us/ajax/autocompleter) are all dead links. It appears that the demo sub-sub domain is not valid. Searching this group shows there has been discussion of this issue but no resolution. Comments like dead links should have been removed smack of someone who has not actually looked at the page which in fact has dead links : http://wiki.github.com/madrobby/scriptaculous/demos --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Working Demo?
Scripty2 is in alpha stages and may be out soon it might be worthwhile holding out for a stable release of that. -- From: Thomas.Paine tpa...@gmail.com Sent: Monday, November 16, 2009 1:35 PM To: Prototype script.aculo.us prototype-scriptaculous@googlegroups.com Subject: [Proto-Scripty] Working Demo? Before investing time and energy into implementing your auto complete addon I would like to see a working demo of it. The links I have found to your demo (http://demo.script.aculo.us/ajax/autocompleter) are all dead links. It appears that the demo sub-sub domain is not valid. Searching this group shows there has been discussion of this issue but no resolution. Comments like dead links should have been removed smack of someone who has not actually looked at the page which in fact has dead links : http://wiki.github.com/madrobby/scriptaculous/demos --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Working Demo?
You do know these projects are done for free dont you? I am sorry to point out that your comments are a little demanding against an open source project .. It takes minutes to setup your own demo so i would advise you experiment and see if it works for you. Alex Mcauley http://www.thevacancymarket.com - Original Message - From: Thomas.Paine tpa...@gmail.com To: Prototype script.aculo.us prototype-scriptaculous@googlegroups.com Sent: Monday, November 16, 2009 7:35 PM Subject: [Proto-Scripty] Working Demo? Before investing time and energy into implementing your auto complete addon I would like to see a working demo of it. The links I have found to your demo (http://demo.script.aculo.us/ajax/autocompleter) are all dead links. It appears that the demo sub-sub domain is not valid. Searching this group shows there has been discussion of this issue but no resolution. Comments like dead links should have been removed smack of someone who has not actually looked at the page which in fact has dead links : http://wiki.github.com/madrobby/scriptaculous/demos --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] onClick vs Element.observe
Hi all,
I have an app that is going to put out a list of items onto a page
and each one has a number of click targets. Now i could setup the
event handler in one of two ways.
1. add it into the template that is rendered with the following code
div onclick=doIt() id=item_1 class=itemItem Name 1/div
or i could do the following
2. Add it using a selector and a script
$$(.item).each(function(element){element.observe('click', doIt);});
Are there any issues with option 1 or 2 and which is more performant
and cross browser compatible. I think 1 is more performant but not
sure it works in all browsers.
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: Insert , Defer and Is there a better way?
This is not during DOM load but post dom load where i am trying to
insert more dom elements into the tree that i am seeing things not
always load.
On Nov 5, 12:37 pm, Matt Foster mattfoste...@gmail.com wrote:
In taking a second look at your code...
Are you using the F function recursively to wait for the DOM to be
loaded and your area element to be available?
you can use many other approaches...
Prototype
$(document).observe(dom:loaded, function()...);
Traditional
window.onload = function()...
By executing your code in those methods, you can be sure that DOM
elements are loaded and ready for manipulation via Javascript.
--
http://positionabsolute.net
On Nov 5, 3:22 pm, Matt Foster mattfoste...@gmail.com wrote:
Hey Kiran,
Function.defer is simply delegating the functions execution to
Function.delay which in the end delegates it to a wrapper of
window.setTimeout.
By using defer it enforces the timeout to be a value of 0.01 which is
just enough to hiccup the browser's procedural processing.
If your application relies on this element to be inserted, avoid the
defer and you'll be sure the content is loaded after execution of
insert.
--
http://positionabsolute.net
On Nov 2, 7:41 pm,phegaropheg...@gmail.com wrote:
HI T.J,
I'm sorry but are you asking for more than what is above? I can
write a simple page that puts together the HTML and JS listed above.
Is that what you want?
Kiran
On Oct 30, 2:22 am, T.J. Crowder t...@crowdersoftware.com wrote:
Hi Kiran,
It sounds like you've already put together a minimalist test case,
would you post it (e.g., to Pastie[1] or similar)? I haven't run into
a situation where a single defer wasn't sufficient, but I also haven't
tested extensively on Mac OS.
Cheers,
--
T.J. Crowder
Independent Software Consultant
tj / crowder software / comwww.crowdersoftware.com
On Oct 30, 7:19 am,phegaropheg...@gmail.com wrote:
Hi all,
This might be a more generic browser/javascript questions than a
prototype specific quesiton but i thought it would better to ask here
because you all tend to really understand javascript and browsers in a
ton of detail. So here goes.
If i execute the following code:
HTML:
div id=area/div
Javascript:
$('area').insert({bottom: div id=inserted/div});
var count = 0;
var f = function() {
if ($('inserted') == null) {
console.log(not there);
count++;
if (count 50) {
$('area'.insert({bottom: div id=inserted/
div});
count = 0;
}
f.defer();
} else {
console.log(there);
}
};
f();
Result:
Most of the time it just shows:
there
but some of the time it does this
not there
not there
not there
there
I am assuming because the insert is something that is queued and the
browser then inserts the nodes into the DOM in its next event loop. I
know that webkit is a single threaded so this makes sense that
sometimes its not there and then it gets there, so really i guess i
have to wait till its there before i can do the next thing on that
inserted node. What about firefox and IE? Are they all single threaded
in the same way? What happens in Chrome?
Sometimes i see the following happen also which is really concerning
to me:
not there
not there
... 50 times
not there
there
It happens every so often on webkit (mac os) and on iPhone webkit and
i can reproduce it pretty easily. I have built something simple that
will do this but all this seems a little crazy to me because when i
look at others code they dont even take this into account. They never
way for DOM elements to show up when inserting HTML text into a DOM
element.
Any answers/suggestions would be super helpful.
Kiran
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: Working Demo?
Yes, I do know that and I'm sorry I was rude in my original post. There are just quite a few options out there and a working demo helps me weed out the chafe so to speak. It would also help your adoption rate and in turn increase the number of people contributing to the software. A broken link however tends to make me nervous and I wonder how well tested the software is. Since I plan on using this on a site that gets considerable traffic things like that are important to me. -t On Nov 16, 2:36 pm, Alex McAuley webmas...@thecarmarketplace.com wrote: You do know these projects are done for free dont you? I am sorry to point out that your comments are a little demanding against an open source project .. It takes minutes to setup your own demo so i would advise you experiment and see if it works for you. Alex Mcauleyhttp://www.thevacancymarket.com - Original Message - From: Thomas.Paine tpa...@gmail.com To: Prototype script.aculo.us prototype-scriptaculous@googlegroups.com Sent: Monday, November 16, 2009 7:35 PM Subject: [Proto-Scripty] Working Demo? Before investing time and energy into implementing your auto complete addon I would like to see a working demo of it. The links I have found to your demo (http://demo.script.aculo.us/ajax/autocompleter) are all dead links. It appears that the demo sub-sub domain is not valid. Searching this group shows there has been discussion of this issue but no resolution. Comments like dead links should have been removed smack of someone who has not actually looked at the page which in fact has dead links :http://wiki.github.com/madrobby/scriptaculous/demos --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Draggable failing after first drag in Firefox?
Hi David,
Whaddaya know, upgrading worked!
Thanks for your suggestion, I will make sure I'm on the correct
version before darkening the group's door again!
Cheers
WoolyG
On Nov 17, 1:13 am, david david.brill...@gmail.com wrote:
Hi WoolyG,
I'm sure that this code will work on FF 3.0.15.
Do you have any error in firebug?
You could try tpo dowload prototype 1.6.1 and scriptaculous 1.8.3 to
test if it's work ?
--
david
On 16 nov, 10:22, woolyg woo...@gmail.com wrote:
Hi all,
I'm using:
Scriptaculous 1.8.2
Prototype 1.6.0.3
Firefox 3.0.15
I'm stumped with this one. Using the following code within the BODY
element:
div id=drag_demo_1 style=width:80px; height:80px; cursor:move;
background:#7baaed; border:1px solid #333;/div
script type=text/javascript
new Draggable('drag_demo_1');
/script
I'm finding that in Firefox, the div drags fine on the first effort,
but then upon the second effort, it remains stationary.
In IE8, the div drags every time I attempt to use it.
Aside from the standard HTML and calling the prototype scriptaculous
JS files, this is the only code on the page, and it still fails!
Stranger still, when I use FF to go
tohttp://wiki.github.com/madrobby/scriptaculous/draggable
and try the first draggable demo there, it works fine (though I am
unsure as to which version of Prototype Scriptaculous MadRobby is
using).
Has anyone seen this before? Can anybody comment?
All replies appreciated.
Thanks
WoolyG- Hide quoted text -
- Show quoted text -
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
