Databases
StackOverflow2013
Postsdbo
POForce UI repaint in Webkit (Safari & Chrome) right before Synchronous "Ajax" request
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POForce UI repaint in Webkit (Safari & Chrome) right before Synchronous "Ajax" request
    primarykey
    data
    text
    <p>In a simple Ajax based website we are making some HttpRequests requests synchronously (I realize "synchronous Ajax" is somewhat of an oxymoron). The primary reason this is being done synchronously vs. asynchronously is in order to simplify the programming model for some of those involved (long story).</p> <p>Anyway, we want to be able to make a styling change (specifically, overlay the screen with semi transparent white as Google search does) right before the request is made, and then take it away when results come back. Essentially this looks like:</p> <pre><code>load:function(url) { .... busyMask.className="Shown"; //display=block; absolute positioned full screen semi-transparent var dta=$.ajax({type:"GET",dataType:"json",url:url,async: false}).responseText; busyMask.className="Hidden"; //sets display=none; ... return JSON.parse(dta); } </code></pre> <p>It is well known a synchronous requests will lock the UI. So not surprisingly, the white overlay never shows up in Safari and Chrome (it does in Firefox interestingly). I've tried slowing the response way down and using a pink overlay so that it will be painfully obvious, but it just won't update the UI until after the request is complete. Leaving the 'busyMask.className="Hidden"' part out will show the mask-- but only after the ajax request is complete.</p> <p>I've seen many many tricks for forcing the UI to repaint (e.g. <a href="https://stackoverflow.com/questions/924681/why-hourglass-not-working-with-synchronous-ajax-request-in-google-chrome">Why HourGlass not working with synchronous AJAX request in Google Chrome?</a>, <a href="http://ajaxian.com/archives/forcing-a-ui-redraw-from-javascript" rel="nofollow noreferrer">http://ajaxian.com/archives/forcing-a-ui-redraw-from-javascript</a>), but they all seem to be in conjunction with trying to show actual "permanent" DOM or styling updates, not with temporarily showing a style change while a synchronous request is made.</p> <p>So is there a way to do this or am I fighting a losing battle? It may be that we'll just need to switch to asynchronous requests on a case by case basis for the worst performing requests, which might be a decent way to tackle the learning curve issue... But I'm hoping there is an outside the box answer here.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USjwl
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POForce UI repaint in Webkit (Safari & Chrome) right before Synchronous "Ajax" request
      1. USjwl
      1. VTBountyStart
    2. VO
      singulars
      1. POForce UI repaint in Webkit (Safari & Chrome) right before Synchronous "Ajax" request
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POForce UI repaint in Webkit (Safari & Chrome) right before Synchronous "Ajax" request
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload