{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/webvtt/issues/467","repository_url":"https://api.github.com/repos/w3c/webvtt","labels_url":"https://api.github.com/repos/w3c/webvtt/issues/467/labels{/name}","comments_url":"https://api.github.com/repos/w3c/webvtt/issues/467/comments","events_url":"https://api.github.com/repos/w3c/webvtt/issues/467/events","html_url":"https://github.com/w3c/webvtt/issues/467","id":463904017,"node_id":"MDU6SXNzdWU0NjM5MDQwMTc=","number":467,"title":"[IR] parsing: region lines","user":{"login":"gkatsev","id":535884,"node_id":"MDQ6VXNlcjUzNTg4NA==","avatar_url":"https://avatars0.githubusercontent.com/u/535884?v=4","gravatar_id":"","url":"https://api.github.com/users/gkatsev","html_url":"https://github.com/gkatsev","followers_url":"https://api.github.com/users/gkatsev/followers","following_url":"https://api.github.com/users/gkatsev/following{/other_user}","gists_url":"https://api.github.com/users/gkatsev/gists{/gist_id}","starred_url":"https://api.github.com/users/gkatsev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gkatsev/subscriptions","organizations_url":"https://api.github.com/users/gkatsev/orgs","repos_url":"https://api.github.com/users/gkatsev/repos","events_url":"https://api.github.com/users/gkatsev/events{/privacy}","received_events_url":"https://api.github.com/users/gkatsev/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-07-03T18:50:55Z","updated_at":"2019-07-04T15:18:02Z","closed_at":null,"author_association":"COLLABORATOR","body":"The [region lines](https://github.com/web-platform-tests/wpt/blob/master/webvtt/parsing/file-parsing/tests/regions-lines.html) text parsing test is failing.\r\nSome of the assertions pass but some fail due to the usage of very large number values. Safari is clamping the value to the max integer value while Firefox returns a 0. The spec just says to interpret the value as an integer but provides no guidance on it. This potentially means there's no way to test these edge cases. Though, may not be necessary.\r\nFirefox's strict parser and Safari's non-standard implementations prevent the test from passing."},"comment":{"url":"https://api.github.com/repos/w3c/webvtt/issues/comments/508516431","html_url":"https://github.com/w3c/webvtt/issues/467#issuecomment-508516431","issue_url":"https://api.github.com/repos/w3c/webvtt/issues/467","id":508516431,"node_id":"MDEyOklzc3VlQ29tbWVudDUwODUxNjQzMQ==","user":{"login":"css-meeting-bot","id":27466577,"node_id":"MDQ6VXNlcjI3NDY2NTc3","avatar_url":"https://avatars0.githubusercontent.com/u/27466577?v=4","gravatar_id":"","url":"https://api.github.com/users/css-meeting-bot","html_url":"https://github.com/css-meeting-bot","followers_url":"https://api.github.com/users/css-meeting-bot/followers","following_url":"https://api.github.com/users/css-meeting-bot/following{/other_user}","gists_url":"https://api.github.com/users/css-meeting-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/css-meeting-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/css-meeting-bot/subscriptions","organizations_url":"https://api.github.com/users/css-meeting-bot/orgs","repos_url":"https://api.github.com/users/css-meeting-bot/repos","events_url":"https://api.github.com/users/css-meeting-bot/events{/privacy}","received_events_url":"https://api.github.com/users/css-meeting-bot/received_events","type":"User","site_admin":false},"created_at":"2019-07-04T15:18:02Z","updated_at":"2019-07-04T15:18:02Z","author_association":"MEMBER","body":"The Timed Text Working Group just discussed `[IR] parsing: region lines webvtt#467`, and agreed to the following:\n\n* `SUMMARY: Probable proposal will be to use closest value algorithm, needs implementor input`\n\n<details><summary>The full IRC log of that discussion</summary>\n&lt;nigel> Topic: [IR] parsing: region lines webvtt#467<br>\n&lt;nigel> github: https://github.com/w3c/webvtt/issues/467<br>\n&lt;nigel> Gary: When parsing the WebVTT file with region lines being some very large value or very small value, that is<br>\n&lt;nigel> .. outside of the int range, Safari I think returns max integer but Firefox returns a zero.<br>\n&lt;nigel> .. I think that is technically correct based on reading the spec, because it says \"interpret as an integer\".<br>\n&lt;nigel> Nigel: Which is correct?<br>\n&lt;nigel> Gary: I think both of them are. I don't think one is necessarily more correct.<br>\n&lt;nigel> .. There's nothing beyond \"interpret\".<br>\n&lt;nigel> Nigel: Is that not an interop problem?<br>\n&lt;nigel> Gary: Maybe, and that's why I thought this is worth talking about, because I'm not sure.<br>\n&lt;nigel> Nigel: Any immediate views on this? I don't have an answer.<br>\n&lt;nigel> Gary: The HTML spec for parsing floating points says if too large or small to use the closest available number to it.<br>\n&lt;nigel> .. To me that seems like the correct decision, but at the same time, basically I guess the question to answer now is<br>\n&lt;nigel> .. should this hold up the current at risk CR or should we just get that out and then figure out what to do with this,<br>\n&lt;nigel> .. alongside everything else.<br>\n&lt;nigel> Nigel: It doesn't help with exiting CR because there's a failing test.<br>\n&lt;nigel> Gary: Yes<br>\n&lt;nigel> Nigel: It looks like Firefox would need to change if your instinct is right. Is it worth talking to anyone at Mozilla?<br>\n&lt;nigel> Gary: Yes I can try or ask Philippe to find someone.<br>\n&lt;nigel> Nigel: Sounds like a good way forward.<br>\n&lt;nigel> Atsushi: I have nothing for today, but I also work for i18n WG and would like to check with them.<br>\n&lt;nigel> SUMMARY: Probable proposal will be to use closest value algorithm, needs implementor input<br>\n</details>\n"}}
{"actor":{"display_login":"css-meeting-bot"}}