328702 - Option to make main throbber a spin during submission

Status: RESOLVED WONTFIX

(Core Graveyard :: XForms, enhancement)

Description

[Allan Beaufour]

As noted in:
http://www.beaufour.dk/blog-archives/2006/02/flickr_search_firefox.html#comments
it could maybe be nice to have an option to make the main throbber spin on submission activity.

This is related to bug 312418, which is about the same thing for XMLHttpRequest, and the same pro/con arguments apply here -- so it's not directly depending on that bug, but I'm pretty sure beltzner et.al has the same opinions about this too.

Comment 1

[Doron Rosenberg (IBM)]

It sounds good to me, but the question is, what about background submissions, IE submissions the user shouldn't be noticing?  We might want to do this only if the user clicks on a submit element perhaps?

Comment 2

[Allan Beaufour]

(In reply to comment #1)
> It sounds good to me, but the question is, what about background submissions,
> IE submissions the user shouldn't be noticing?  We might want to do this only
> if the user clicks on a submit element perhaps?

A value change could trigger a submission, which the user will be waiting for. On the other hand, then the form author could display something instead of relying on the UA to show it... maybe only submit button.

Personally I would actually like it to spin on all submission activity. It's my browser, I want to know when it is sending or retrieving data..

Comment 3

[aaronr]

(In reply to comment #2)
> (In reply to comment #1)
> > It sounds good to me, but the question is, what about background submissions,
> > IE submissions the user shouldn't be noticing?  We might want to do this only
> > if the user clicks on a submit element perhaps?
> 
> A value change could trigger a submission, which the user will be waiting for.
> On the other hand, then the form author could display something instead of
> relying on the UA to show it... maybe only submit button.
> 
> Personally I would actually like it to spin on all submission activity. It's my
> browser, I want to know when it is sending or retrieving data..
> 


Yep, I think that limiting to the submit element is too restrictive, too.  The form author could use the send action in response to a DOMActivate on a trigger that says 'submit' in the label but the author chose not to use the actual submit element for some reason.  That is pretty nit-picky and something that the form author isn't likely to catch.  If we do make the throbber spin, we should also put something in the status bar in case the user wonders why the throbber is spinning.

Comment 4

[David Bolter [:davidb] (NeedInfo me for attention)]

RIP xforms