Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>this won't work too well 'as is'. the problem with event bubbling (and with programmatic firing of events) is that it may need the event object to be 'real' in order for it to contain <code>event.target</code> that is being matched against the relay string. also, <code>document.id("color").fireEvent()</code> won't work as color itself has no event attached to it.</p> <p>to get around this, you fake the event on the parent listener by passing an event object that contains the target element like so:</p> <pre><code>document.id("listener").fireEvent("change", { target: document.id("color") }); </code></pre> <p>view in action: <a href="http://www.jsfiddle.net/xZFqp/1/" rel="noreferrer">http://www.jsfiddle.net/xZFqp/1/</a></p> <p>if you do things like event.stop in your callback function then you need to pass on <code>{target: document.id("color"), stop: Function.from}</code> and so forth for any event methods you may be referencing but the event delegation code is only interested in <code>target</code> for now.</p>
    singulars
    1. This table or related slice is empty.
    1. POMooTools - Programmatically fired events not working with event delegation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDimitar Christoff
    1. USDimitar Christoff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMooTools - Programmatically fired events not working with event delegation
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for this approach Dimitar. However, I don't feel very comfortable firing the event on the parent directly cause that's getting too friendly with the internal workings. Also, would I be wrong to say MooTools doesn't use the DOM event dispatching mechanism, and stores event handlers for each element in the element store?
      singulars
      1. PO
      1. USAnurag
    2. COI don't see a problem with firing the event through the parent listener. To be honest, the mootools core team are the first to admit that the current implementation of event delegation leaves things short of brilliant. I cannot comment on what is forthcoming in the near-ready 1.3 or almost-near-ready mootools 2.0 but you are correct in that events are basically in element storage under events (so you can do `var myEvents = this.retrieve("events");` and get an object with the event name as key, like `myEvents.click` and can explore it further under click.keys to find the stored functions.
      singulars
      1. PO
      1. USDimitar Christoff
    3. COI would also say that the native method you have used for dispatching the event is is not cross-browser compliant (fails FF) and this kind thing defeats the purpose of using a framework when you need to cater for every possible way of achieving this for all browser engines... Having said that, if you get anywhere with this, may be worth submitting it on github as a new method of the Event class, like `fireNativeEvent: function(eventType)`. Good luck
      singulars
      1. PO
      1. USDimitar Christoff
 

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