Thanks Aaron
moving those two line before the check whether there are any lightbox
links available did the trick as well.
as to the http3%A// problem, there is the following line of code in
lightbox: this.image.setStyle('backgroundImage', 'url('+escape
(this.images[this.activeImage][0])+')'); - it's around line 264 in the
nextEffect function - if I remove the escape function, the picture is
finally showing up!
once again, thanks for your professional response
On Dec 29, 10:05 pm, Aaron Newton <[email protected]> wrote:
> Let's settle down people. At the very least, this isn't a conversation that
> needs to be broadcast to every subscriber of this mailing list (nearly 2000
> people). Take if offline or, better yet, just focus on what you are doing
> and not what others are up to.
>
> Now, the lightbox thing.
>
> First, the original Lightbox (non-mootools) was something that just happened
> to all the links on the page. It wasn't something you instantiated.
> Consequently, when I ported it, I made it behave exactly the same way
> (actually, my version is an upgrade of someone else's port, but I digress).
> But my version does allow you to create instances and set options.
>
> So if you are adding links after the fact, just create a new instance and
> pass in the anchors. It's no big deal.
>
> On Tue, Dec 29, 2009 at 9:27 PM, Sanford Whiteman <
>
>
>
> [email protected]> wrote:
> > > what's your problem sanford
>
> > Close out the highlight.dispose thread that you got 3-4 people
> > accepting into as a MooTools "IE incompatibility" problem, when
> > actually the behavior was the same in every browser. And this would
> > have been instantly obvious if you had put up a MooShell for
> > verification.
>
> > On the other hand, if you still stand behind that bug, enter it in
> > Lighthouse and put a proof-of-concept for it in MooShell.
>
> > > there seems to be a bug in the [Lightbox] script
>
> > Then enter it in Lighthouse and put a proof-of-concept in MooShell.
>
> > This isn't difficult to reason out. MooShell is a lab to demonstrate
> > features and misfeatures, good and bad code, in an environment that
> > actually runs JavaScript. I don't know about your e-mail client, but
> > mine doesn't run code.
>
> > -- S.
