Yeah, those poor IE users will just have to read the "if your file did
not download, click here" message and do the download click themselves
if they stop the meta refresh bah, IE ... hate it.
On Dec 20, 2008, at 3:48 PM, John Huss wrote:
Be careful, i think this pops up a warning
Be careful, i think this pops up a warning in IE.
On Dec 20, 2008, at 10:19 AM, Kieran Kelleher
wrote:
Susanne, that is brilliant!
What a simple solution that is very elegant from the user's point of
view . the thought never crossed my mind to use the Refresh
header to trigger a si
Susanne, that is brilliant!
What a simple solution that is very elegant from the user's point of
view . the thought never crossed my mind to use the Refresh header
to trigger a single download response on refresh! This is exactly the
kind of idea I was looking for and it works great whi
Hi Kieran,
you could return the page to be displayed to the user with an
meta-reload at the top for downloading the file with a download action.
The meta-reload is only displayed once with a flag set from the finished
action and reset from the download-action. This should work as long as
the
Hi Miguel,
I have no problem using AjaxProgress, long response updating, etc for
"normal" long response tasks where a *single* WOActionResults gets
fired at the end of the long response task to take user to whatever
page I want to push them to . the question is what behaviour to
have
Hi!
One way we use to solve those problems is to have a part of the
page updating every X seconds (it may be an AjaxUpdateContainer or
so). When possible, we show up the percentage of the processing on
that AUC.
Yours
Miguel Arroz
On 2008/12/19, at 17:55, Kieran Kelleher wrote:
L
Looking for UI behaviour ideas When I have a case of large
file download that needs a long response preparation scenario due to
file prep time, I normally do one of these 2:
1) Open a popup Window saying sth like "please wait while we prepare
your file..." and that popup runs the l
