{"comment":{"url":"https://api.github.com/repos/w3c/webappsec-suborigins/comments/20107724","html_url":"https://github.com/w3c/webappsec-suborigins/commit/36fa91042122a7c0db31db9a6fee9c409bee0196#commitcomment-20107724","id":20107724,"user":{"login":"metromoxie","id":401207,"avatar_url":"https://avatars.githubusercontent.com/u/401207?v=3","gravatar_id":"","url":"https://api.github.com/users/metromoxie","html_url":"https://github.com/metromoxie","followers_url":"https://api.github.com/users/metromoxie/followers","following_url":"https://api.github.com/users/metromoxie/following{/other_user}","gists_url":"https://api.github.com/users/metromoxie/gists{/gist_id}","starred_url":"https://api.github.com/users/metromoxie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/metromoxie/subscriptions","organizations_url":"https://api.github.com/users/metromoxie/orgs","repos_url":"https://api.github.com/users/metromoxie/repos","events_url":"https://api.github.com/users/metromoxie/events{/privacy}","received_events_url":"https://api.github.com/users/metromoxie/received_events","type":"User","site_admin":false},"position":188,"line":769,"path":"index.bs","commit_id":"36fa91042122a7c0db31db9a6fee9c409bee0196","created_at":"2016-12-07T18:12:54Z","updated_at":"2016-12-07T18:12:54Z","body":"I'm pretty sure that behavior is invalid according to the HTML spec, which seems pretty clear to me to leave the door open to getters and setters, so, yes, we should probably update HTML with this to make that explicit. @annevk's opinion would be great here, too.\r\n\r\nCan you be more specific about the browsers that do that and under what conditions? That is, under what types of cookie-averse documents do they fail to allow getters and setters? There are relatively few cases where cookie-aversity exists currently, so I'm surprised to hear that."}}
{"actor":{"display_login":"metromoxie"}}