![]() ![]() component oncomplete and then queue oncomplete will be fired. NOTE: These event handlers which are defined in a queue should be fired together with handlers on the components (the components handlers should not override queues ones).Īlso local component events will be fired and the queue events will fired after them. And the element which was a source of the request will be available using "this".įired after responce comes before DOM updates Thus queue will be accessible using request.queue. In this event handler request object will be passed as a parameter. (onsubmit on the form or on the component only could cancel the request.) request object passed as a parameter. But new request waits till the previous response in order to prevent parallel requests.ĭefines status component which will be activated on any request from this queue. If true it abborts a request client processing if new similar request comes to queue. Standard behavior of the attribute : if the request is sent and response is not returned within the timeframe defined in this attribute - the request is aborted, and the next one is sent. The amount of time an item can be in the queue before the sent event will be aborted and dropped from the queue. It should be fired after the request is generated, a request object and queue should be passed as parameters.ĭefining requestDelay="1000" on the queue means that all the requests which fired using this queue will have this 1 sec delay. In all of these cases the onSizeExceeded callback will be triggered. A user should take care about new events by himself, a request and a queue should be passed as a parameter to handler.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |