From: acoleman616 on
Hello all,

I'm currently having a dilemma. I'm using an iframe as a target to
handle a form submit to allow users to submit file uploads without
requiring a page reload. What I want to do is this: when the user
clicks the submit button, I want a "cancel" button to appear -
clicking that "cancel" button will then kill/cancel the form submit
currently in progress. Any thoughts?

I realize that you normally cancel a submit with onsubmit(), but
that's not the case here since the submit is already in progress in
this case.

Thanks in advance for any help.
From: David Mark on
On Jan 5, 8:11 pm, acoleman616 <acoleman...(a)gmail.com> wrote:
> Hello all,
>
> I'm currently having a dilemma.  I'm using an iframe as a target to
> handle a form submit to allow users to submit file uploads without
> requiring a page reload.  What I want to do is this: when the user
> clicks the submit button, I want a "cancel" button to appear -
> clicking that "cancel" button will then kill/cancel the form submit
> currently in progress.  Any thoughts?

Yes. It can't be done. And why is a page reload a problem? If your
pages are lean enough, the user won't know the difference. The
typical Website today requires a reload every time the user clicks the
back (or forward) button. Weed those out first as browser navigate
far more often than they upload. ;)
From: Jorge on
On Jan 6, 2:29 am, David Mark <dmark.cins...(a)gmail.com> wrote:
> (...)  The
> typical Website today requires a reload every time the user clicks the
> back (or forward) button. (...)

Not in current Safaris nor FireFoxes.
--
Jorge.

From: rf on

"acoleman616" <acoleman616(a)gmail.com> wrote in message
news:58910f54-5100-466a-af03-cb0275744435(a)s31g2000yqs.googlegroups.com...
> Hello all,
>
> I'm currently having a dilemma. I'm using an iframe as a target to
> handle a form submit to allow users to submit file uploads without
> requiring a page reload. What I want to do is this: when the user
> clicks the submit button, I want a "cancel" button to appear -
> clicking that "cancel" button will then kill/cancel the form submit
> currently in progress. Any thoughts?

Your browser has a cancel button in its toolbar.


From: David Mark on
On Jan 5, 8:35 pm, Jorge <jo...(a)jorgechamorro.com> wrote:
> On Jan 6, 2:29 am, David Mark <dmark.cins...(a)gmail.com> wrote:
>
> > (...)  The
> > typical Website today requires a reload every time the user clicks the
> > back (or forward) button. (...)
>
> Not in current Safaris nor FireFoxes.

You are very confused, Jorge (as usual). Virtually every major
browser offers fast history navigation (and has for years). You just
don't see it on the Web much due to poorly designed scripts.

The problem is that most "major" libraries hang unload listeners on
the body for no reason, which requires documents to reload on
navigation (otherwise they'd be crippled as all of the listeners have
been detached). As we've discussed here, the listeners aren't the
problem and the real problem (circular references involving host
objects) is easily avoided at the design stage. Sound familiar?

The "solution" that was in vogue for a while was to try to cram sites
and applications into one document, thereby eliminating navigation
altogether. Of course, that short-circuits other things as well (e.g.
bookmarks), "requiring" further hacks, calls to standardize unneeded
events (e.g. hash change), etc.

It's a backwards strategy that discounts what browsers do well (and
what they were designed to do), focusing instead on what they do
poorly (and were never designed to do). Eventually, the whole idea of
applications running on top of documents in browsers will go by the
wayside (particularly since most of these apps are built on top of
scripts that can't even _read_ documents). ;)