07-21-2014 11:50 AM
Just testing out IE10 using the stored process web app.
In IE 8, when I clicked the "Run" button to launch a STP, there was something on the screen that would pulse or spin or a status bar or that would let me know that the SAS job was running, and results were on the way.
With IE 10, I can't see any indication that work is in progress. ( Other than the RUN button itself gets a black outline when clicked. ) The icon in the tab does NOT spin to indicate the load is in progress.
I'm using the default SPWA interface, URL like:
Guess it could be the tabbed browsing in IE10 that's the issue. Since the tab is for the main frame which lists all the stored processes in the metadata directory, when a stored process runs that tab is not reloading, it's only the frame which displays results which is loading.
But still hoping there is someway I can get IE10 make clear that load is in progress (like the old Netscape beating "N"), so users don't assume the browser has hung. (Without me coding up a custom status bar, like you might for a long running STP).
07-22-2014 09:27 AM
Found this page on Microsoft's site. Looks like other folks have had the same problem in IE 9/10.
When a submit button inside a frame has been pressed, there is no progress bar indicating that work is in progress. The icon in the tab does not spin. Very unfortunate.
Still hoping someone will have a work around.
07-22-2014 10:15 AM
Well we like html5....?
This standard does not like frames HTML frame tag (w3schools). Would be nice when all automatic generated html would avoid frames.
07-22-2014 02:09 PM
Yahh but it's silly.
If you mouse over the (empty) status bar at the bottom of IE, the mouse pointer will show you a spinner indicating that something is processing.
Seems like a friendly UI would do that regardless of where the mouse points. So there is some feedback to acknowledge the click.
Even if M$ couldn't figure out how to make an accurate progress bar, they could have done something to indicate "still processing."
May force me to do something like:
07-22-2014 03:10 PM
Perhaps we are still having not much progressed in the Paleolithic
Referring to Jurassic with Don Hendersons post, is forcing me back to Triassic. That is when the IBM on the pangea was a dominant species.
at a server (mainframe). Those browsers (terminals) had a status bar indicating the "processing by server" as "System" with a pseudo interactive mode. Some simple actions could be handled at the plugins (eg java script) some needing to wait for the response. In the multiscreen support mode (frames) there was a problem with that status as just the visible screen could be given.
Sorry for this fun, very tempting as those similarities are so big. The reason for leaving frames out in html-5 is probably the same contradiction and the ease of breaking out the frames to each part. It is the decision of W3.org to do that. A everyone is going that direction IE is moving also to that. Do not be surprised of old features going to be history.
The idea of putting an empty message or start message in your screen where later the output should come, sounds to me as reasonably good.
I suppose some html interactive approaches are thinking in the same direction (AJAX).
The classic one is: "this page is intentionally left blank"