{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/css-houdini-drafts/issues/193","repository_url":"https://api.github.com/repos/w3c/css-houdini-drafts","labels_url":"https://api.github.com/repos/w3c/css-houdini-drafts/issues/193/labels{/name}","comments_url":"https://api.github.com/repos/w3c/css-houdini-drafts/issues/193/comments","events_url":"https://api.github.com/repos/w3c/css-houdini-drafts/issues/193/events","html_url":"https://github.com/w3c/css-houdini-drafts/issues/193","id":154532533,"number":193,"title":"[css-typed-om] Rename CSSTokenStream to something that doesn't talk about tokens","user":{"login":"tabatkins","id":682840,"avatar_url":"https://avatars.githubusercontent.com/u/682840?v=3","gravatar_id":"","url":"https://api.github.com/users/tabatkins","html_url":"https://github.com/tabatkins","followers_url":"https://api.github.com/users/tabatkins/followers","following_url":"https://api.github.com/users/tabatkins/following{/other_user}","gists_url":"https://api.github.com/users/tabatkins/gists{/gist_id}","starred_url":"https://api.github.com/users/tabatkins/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tabatkins/subscriptions","organizations_url":"https://api.github.com/users/tabatkins/orgs","repos_url":"https://api.github.com/users/tabatkins/repos","events_url":"https://api.github.com/users/tabatkins/events{/privacy}","received_events_url":"https://api.github.com/users/tabatkins/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2016-05-12T17:00:46Z","updated_at":"2016-05-23T21:54:58Z","closed_at":null,"body":"It's not really exposing tokens a la Syntax, so we should avoid that word."},"comment":{"url":"https://api.github.com/repos/w3c/css-houdini-drafts/issues/comments/221107931","html_url":"https://github.com/w3c/css-houdini-drafts/issues/193#issuecomment-221107931","issue_url":"https://api.github.com/repos/w3c/css-houdini-drafts/issues/193","id":221107931,"user":{"login":"FremyCompany","id":364405,"avatar_url":"https://avatars.githubusercontent.com/u/364405?v=3","gravatar_id":"","url":"https://api.github.com/users/FremyCompany","html_url":"https://github.com/FremyCompany","followers_url":"https://api.github.com/users/FremyCompany/followers","following_url":"https://api.github.com/users/FremyCompany/following{/other_user}","gists_url":"https://api.github.com/users/FremyCompany/gists{/gist_id}","starred_url":"https://api.github.com/users/FremyCompany/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/FremyCompany/subscriptions","organizations_url":"https://api.github.com/users/FremyCompany/orgs","repos_url":"https://api.github.com/users/FremyCompany/repos","events_url":"https://api.github.com/users/FremyCompany/events{/privacy}","received_events_url":"https://api.github.com/users/FremyCompany/received_events","type":"User","site_admin":false},"created_at":"2016-05-23T21:54:58Z","updated_at":"2016-05-23T21:54:58Z","body":"Please accept my sincere excuses for my wording, I agree it is oversized to the problem at stake. I'm very much commenting on this particular issue and not on the general spec, which is very good and has my full support. My aim here is to make it even better by providing feedback as a potential user of the API, nothing else. \r\n\r\nI understand that browsers are not required to parse upfront (I don't think Edge does either), and of course I know that there is a second parse step once the value are being replaced in (this is the whole \"invalid at computation time\" concept). From the author standpoint, though, it doesn't mean this API has to bail out the way it currently does in this case.\r\n\r\nMy problem here is that the current design does not meet the goals the spec sets upon itself. \r\n\r\n> Converting CSSOM value strings into meaningfully typed JavaScript representations and back can incur a significant performance overhead. This specification exposes CSS values as typed JavaScript objects to facilitate their performant manipulation.\r\n\r\nThe goal of the Typed OM API is to make sure we can work with css values in a way that does not required to parse strings in javascript, because this is very inefficient. At least that is my understanding of it, please correct me if I'm wrong.\r\n\r\nIf this is the goal of this API, then I do believe the answer to the case when the value is unparsed and contains variable is insufficient to guarantee this promise. I want to constructively build a better solution for this case, which I think is worth solving. "}}
{"actor":{"display_login":"FremyCompany"}}