{"action":"created","issue":{"url":"https://api.github.com/repos/w3ctag/spec-reviews/issues/100","labels_url":"https://api.github.com/repos/w3ctag/spec-reviews/issues/100/labels{/name}","comments_url":"https://api.github.com/repos/w3ctag/spec-reviews/issues/100/comments","events_url":"https://api.github.com/repos/w3ctag/spec-reviews/issues/100/events","html_url":"https://github.com/w3ctag/spec-reviews/issues/100","id":126318934,"number":100,"title":"Create a document to explain web platform async timing entry-points","user":{"login":"travisleithead","id":2152696,"avatar_url":"https://avatars.githubusercontent.com/u/2152696?v=3","gravatar_id":"","url":"https://api.github.com/users/travisleithead","html_url":"https://github.com/travisleithead","followers_url":"https://api.github.com/users/travisleithead/followers","following_url":"https://api.github.com/users/travisleithead/following{/other_user}","gists_url":"https://api.github.com/users/travisleithead/gists{/gist_id}","starred_url":"https://api.github.com/users/travisleithead/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/travisleithead/subscriptions","organizations_url":"https://api.github.com/users/travisleithead/orgs","repos_url":"https://api.github.com/users/travisleithead/repos","events_url":"https://api.github.com/users/travisleithead/events{/privacy}","received_events_url":"https://api.github.com/users/travisleithead/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-01-13T01:30:46Z","updated_at":"2016-01-13T03:23:01Z","closed_at":null,"body":"As discussed at Melbourne F2F, there are a lot of ways in the platform to schedule stuff, and lots of APIs that do it.\r\n\r\nWe would like to create a document that collates all of these timing entry-points, describes where the timings should happen in relation to other implementation details (layout, painting), and applies fixes for known issues (as noted by @dbaron) with HTML5 task queue description."},"comment":{"url":"https://api.github.com/repos/w3ctag/spec-reviews/issues/comments/171149462","html_url":"https://github.com/w3ctag/spec-reviews/issues/100#issuecomment-171149462","issue_url":"https://api.github.com/repos/w3ctag/spec-reviews/issues/100","id":171149462,"user":{"login":"domenic","id":617481,"avatar_url":"https://avatars.githubusercontent.com/u/617481?v=3","gravatar_id":"","url":"https://api.github.com/users/domenic","html_url":"https://github.com/domenic","followers_url":"https://api.github.com/users/domenic/followers","following_url":"https://api.github.com/users/domenic/following{/other_user}","gists_url":"https://api.github.com/users/domenic/gists{/gist_id}","starred_url":"https://api.github.com/users/domenic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/domenic/subscriptions","organizations_url":"https://api.github.com/users/domenic/orgs","repos_url":"https://api.github.com/users/domenic/repos","events_url":"https://api.github.com/users/domenic/events{/privacy}","received_events_url":"https://api.github.com/users/domenic/received_events","type":"User","site_admin":false},"created_at":"2016-01-13T03:23:01Z","updated_at":"2016-01-13T03:23:01Z","body":"I'm a little unclear on the scope here. Maybe the minutes would make it clearer?\r\n\r\n> describes where the timings should happen in relation to other implementation details (layout, painting), and applies fixes for known issues (as noted by @dbaron) with HTML5 task queue description.\r\n\r\nThis sounds like it would be best done not as a separate document but as a pull request to modify https://html.spec.whatwg.org/#processing-model-8.\r\n\r\n> We would like to create a document that collates all of these timing entry-points\r\n\r\nThis might be a worthwhile guidance document explaining when and how specs should use HTML's algorithms to perform their work.\r\n\r\n> perhaps the need for a better developer-facing way to prioritize tasks.\r\n\r\nThere are actually some discussions on this happening right now between myself and the Angular team. We hope to send a proposal as an issue on whatwg/html shortly (next few days probably). Stay tuned!"}}