orstavik / joicomponents Goto Github PK

So that the original event is processed before the gesture events? To do so we would need to async que the gesture event. But. If we do so, then we might be able to stop the gesture by stopping the propagation of the trigger touchevent above the gesture making event. This I think would be bad, it would be confusing.

• styleCallback

• layoutCallback

• efficient que for calling the style and layout calculations sparingly. Make que system that works on HTMLElement.compareDocumentPosition. https://developer.mozilla.org/en-US/docs/Web/API/Node/compareDocumentPosition

• This should likely be dynamic, but perhaps only dynamic once.
  If one element with styleCallback creates other elements with styleCallback during a styleCallback que flush, then those new elements should be added at the end. No elements should be run twice in the styleCallback que.

• efficient, run once every raf and add a manual trigger?

• efficient, add a register of previous values, so that if no change since last call, the callback will not be triggered.

• demo for styleCallback

• demo for layoutCallback

• unitTest for styleCallback

• unitTest for layoutCallback

Can we wrap the .preventDefault and .stopPropagation methods in a good way?
Does this look ok?
Do we need to process something in the submit event that we do not have? such as relList?

Events,

• EventOrganizer (a href, form) the target of the new event.
• EventSupervisor (base) contains additional information for the new event, outside of the event organizer.
• EventParticipant (input) contains additional information for the new event, inside the event organizer.
• EventTrigger (buttton) trigger for the composed event, should be inside the event organizer.
• https://codepen.io/orstavik/pen/PXeyWw?editors=1001