Thank you Karl. It works like charm.
Dear All,
I have an object with mouse over and mouse out events. It fires
display certain other box (almost like tooltip):
box.fadeIn("slow")
box.fadeOut("slow")
It works absolutely fine unless mouse passed over the object without
intention to stop. Then it triggers full scenario, complete fadi
FYI: Semi-colons are missing on lines 87 & 605 of the form plugin,
thus making it hard to compress/obfuscate.
Karl, that was exactly it - a trailing comma. Thanks a bunch!
-stan
On Nov 13, 12:27 pm, Karl Swedberg <[EMAIL PROTECTED]> wrote:
> I have never had this problem before on any browser. Do you have a
> test page you could show us? It could be that one of your JavaScript
Hi, thanks for replying. I'm on an Intranet, so I can't show you, but
I'll comment out all the code in the two files except for the
document.ready() calls and see if I can trace it down. Thanks again.
-stan
On Nov 13, 12:27 pm, Karl Swedberg <[EMAIL PROTECTED]> wrot
Hi,
Newbie here. I have two JS files, common.js and homepage.js. Both
have calls to $(document).ready(). Using FF, both $(document).ready()
methods execute, but in IE6, only one does. Is this a known problem?
Thanks,
Stan McFarland
of the various sources, and
I also need to be able to turn a source off, plugin a different source
and then optionally return back to that first source.
Looking forward to feedback from anyone who's faced this predicament
already.
Pax,
- Stan
:28 pm, "Jörn Zaefferer" <[EMAIL PROTECTED]>
wrote:
> Try binding your click-event first, returning false from the function
> you add. Apply the treeview afterwards - in theory, the tree shouldn't
> do anything after your click function got called.
>
> Jörn
>
be called. Ideally, how this would is
click on the hitarea item would fire off the toggler and anything else
would produce in no action from the treeview plugin. I'm not seeing
an easy way of doing this, am I missing something or do you have any
ideas?
Thanks,
Stan
Dan,
Key navigation doesn't work at all - I'm not able to key down or
anything. I wonder if the hotkeys plugin for jQuery might be helpful
in this front since it normalizes key entry behavior? Just a thought.
Thanks again for the stellar plugin.
Pax,
- Stan
On Jun 19, 4:05
I could see this as advantageous to you to get
the plugin more circulated.
All in all, excellent plugin - I will likely use it on a project of my
own.
Pax,
- Stan
On Jun 19, 1:59 pm, "Jörn Zaefferer" <[EMAIL PROTECTED]>
wrote:
> Hey Dan,
>
> great plugin, the interfa
Josh, thanks for the tip. console.log(code) outputs "undefined."
Any other suggestions?
Thanks again,
Stan
On May 5, 7:42 pm, "Josh Nathanson" <[EMAIL PROTECTED]> wrote:
> Stan,
>
> I'd suggest using Firefox with the Firebug extension, and doin
Josh,
It worked with a relative URL, but not the absolute URL. Odd...
-stan
On May 5, 7:42 pm, "Josh Nathanson" <[EMAIL PROTECTED]> wrote:
> Stan,
>
> I'd suggest using Firefox with the Firebug extension, and doing a
> console.log(code) in your cal
l",
function(code) { alert(code[0]); });
I always get back:"code" has no properties
Any suggestions?
Thanks,
Stan McFarland
`
adding opacity hiding it fixes the issue,
fwiw.
Pax,
- Stan
On Apr 16, 9:42 am, "Joel Birch" <[EMAIL PROTECTED]> wrote:
> Hi Reuben,
>
> Superfish doesn't support closing animations. I tried it a while ago
> but experienced too many glitches caused when mousing
Can you clarify what the differences are between this and jTagEditor?
Also... have you ever considered making a single image sprint of the
buttons? That might save some load-time.
Thanks for your work on this plugin, I use it quite a bit and very
appreciative for it!
Pax,
- Stan
On Mar 23, 2
http://stanlemon.net/files/ui.template.js
Thoughts and feedback are much appreciated.
Pax,
- Stan
This plugin works fine until the element that it is placed on is
allowed to scroll. If allowed to scroll, the helperclass drop
location is further and further away from the drag element the more
the element scrolls. Is there a fix for this problem?
18 matches
Mail list logo
