Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, that actually depends on what do you do in your handler and how do you define 1st handler ended moment?</p> <p>For example, if you're doing only sync operations in eventHandler1 then you're sure that eventHandler2 won't get triggered before eventHandler1 finishes. the reason is javascript being single threaded.</p> <p>But, imagine scenario like this: click on button1 triggers eventHandler1 which actually makes ajax request. in that scenario, what do you actually consider as 'end of eventHandler1'? if it is the moment when ajax request returns then certainly eventHandler2 will start (and possible end) execution before eventHandler1 finishes.</p> <p>To put it short: whenever you do sync-only operations > the order is guaranteed.</p> <h2>Added from comments:</h2> <p><a href="http://www.w3.org/TR/DOM-Level-3-Events/#sync-async" rel="nofollow">http://www.w3.org/TR/DOM-Level-3-Events/#sync-async</a> for example, it says: " Each event in this virtual queue must be delayed until the previous event has completed its propagation behavior, or been canceled."</p> <hr> <p>Well, now we're back to the question 'what type of events are we talking about'? As mentioned before: if it's async events then sure the order is not guaranteed. But the original dilemma was about click event and that one is not async but sync. And for sync events documentation clearly states: Events which are synchronous ("sync events") must be treated as if they are in a virtual queue in a first-in-first-out model, ordered by sequence of temporal occurrence, with respect to other events, to changes in the DOM, and to user interaction.</p> <hr> <p>yep, no guarantees. now add javascript being single-threaded into play and you can't get them executing at the same time. but yes, speaking of DOM strictly - there is no guarantee whatsoever which one will happen before.</p> <hr> <p>just one more comment... you might have exactly the same DOM but accessed from Java multi-thread environment. What then?:) then you have to implement your own thread-safe async events handling because you're no more 'protected' by single thread environment as you have with javascript. So, the conclusion, as i see it is that DOM specs does require that sync events are fifo implemented. for async events execution depends on stack/thread implementation. in Javascript, that means that 2 handlers can't overlap but in Java e.g. doesn't have to mean. </p>
    singulars
    1. This table or related slice is empty.
    1. PODo DOM Events Always Run Single Threaded?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdee zg
    1. USdee zg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't understand - why do you think the order is guaranteed? Where does it say so? I'm not asking about calling other asynchronous handlers in the handlers itself.
      singulars
      1. PO
      1. USBenjamin Gruenbaum
    2. COI don't think it. http://www.w3.org/TR/DOM-Level-3-Events/#sync-async for example, it says: " Each event in this virtual queue must be delayed until the previous event has completed its propagation behavior, or been canceled."
      singulars
      1. PO
      1. USdee zg
    3. COYeah, that's the link I linked to in the question linked to this one. It would seem obvious that it would be there but I could not find it stating so anywhere (especially the use of multiple queues there is confusing to me), this might be a problem with me understanding the language well enough though, a specific quote or how you reached the conclusion would really help because I can't seem to be able to deduce this based on the spec. At least not for asynchronous events.
      singulars
      1. PO
      1. USBenjamin Gruenbaum
 

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