Thanks for your response.
No issues at serverside contentType.Response contenttype is application/xls.
Browser is opening save dialog and saveing the response into an .xls file.
My requirement is while downloading data ,browser showd show loading or
downloading message till download will get fin
Did you try this.up('div.bla')?
Walter
On Jan 1, 2009, at 5:43 PM, joris77 wrote:
>
> Hi,
>
> This works in firefox but it doesn't in internet explorer 7 is this an
> issue or am I missing something?
>
>
>
>
>
>
>
> Back
>
>
>
>
> Thanks anyway
>
> >
--~--~-~--~~
Its because FF allows for native prototype extension and IE does not,
such that any referenced element won't have proto's element extension
methods until its been explicitly extended.
Back
But to be honest I wouldn't use that style of event listener, try
something like this...
$$(".bla a").invo
> Browser is opening save dialog and saveing the response into an .xls file.
So your scripts are writing to the clients machine?
Is the data being received over an XHR request?
It wouldn't be the most fluid progress bar, but if it was an XHR you
could increment a progress bar each time it moves
You could use a canvas element or SVG elements.
https://developer.mozilla.org/en/Drawing_Graphics_with_Canvas
https://developer.mozilla.org/en/SVG
Prototype doesn't have much support for either of these options but
they're viable and you could use event listener/dom traversal with the
SVG solut
SlideUp and SlideDown effects need a direct child of the primary
element to use as a way to produce the clipping effect.
http://github.com/madrobby/scriptaculous/wikis/effect-slideup
read the notes about halfway down.
--
http://positionabsolute.net
On Dec 30 2008, 3:34 pm, jeanluca wrote:
>
No doesn't work either but it still works on FireFox
2009/1/2 Walter Lee Davis
>
> Did you try this.up('div.bla')?
>
> Walter
>
> On Jan 1, 2009, at 5:43 PM, joris77 wrote:
>
> >
> > Hi,
> >
> > This works in firefox but it doesn't in internet explorer 7 is this an
> > issue or am I missing some
Matt,
2009/1/2 Matt Foster
>
> Its because FF allows for native prototype extension and IE does not,
> such that any referenced element won't have proto's element extension
> methods until its been explicitly extended.
>
> Back
>
this works thank you very much
>
>
> But to be honest I wouldn't
