{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/webvtt/issues/272","labels_url":"https://api.github.com/repos/w3c/webvtt/issues/272/labels{/name}","comments_url":"https://api.github.com/repos/w3c/webvtt/issues/272/comments","events_url":"https://api.github.com/repos/w3c/webvtt/issues/272/events","html_url":"https://github.com/w3c/webvtt/issues/272","id":117920996,"number":272,"title":"Have tags for specifying color and background color","user":{"login":"zcorpan","id":244772,"avatar_url":"https://avatars.githubusercontent.com/u/244772?v=3","gravatar_id":"","url":"https://api.github.com/users/zcorpan","html_url":"https://github.com/zcorpan","followers_url":"https://api.github.com/users/zcorpan/followers","following_url":"https://api.github.com/users/zcorpan/following{/other_user}","gists_url":"https://api.github.com/users/zcorpan/gists{/gist_id}","starred_url":"https://api.github.com/users/zcorpan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zcorpan/subscriptions","organizations_url":"https://api.github.com/users/zcorpan/orgs","repos_url":"https://api.github.com/users/zcorpan/repos","events_url":"https://api.github.com/users/zcorpan/events{/privacy}","received_events_url":"https://api.github.com/users/zcorpan/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/w3c/webvtt/labels/addition/proposal","name":"addition/proposal","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-11-19T22:16:42Z","updated_at":"2015-11-23T15:36:28Z","closed_at":null,"body":"See https://github.com/w3c/webvtt/pull/261#issuecomment-158187662\r\n\r\nAgain I suppose this would be needed on the cue level as well as on the element level, if it should be possible to override the default background color.\r\n\r\nI don't particularly like adding new elements for color, it seems like it would be better to be able to set colors on any element, like you can set classes on any element.\r\n\r\nWe could allow color specifiers at the end of start tags, as annotations. For elements that already require annotations, we could make a \"#\" switch from annotation to color. (It would be possible to write stylesheets that work in legacy clients using `^=` attribute selector, e.g. `v[voice^=Roger]`.)\r\n\r\n```\r\nWEBVTT\r\n\r\n00:00:00.000 --> 00:00:10.000.foo.bar align:left #FFF #000\r\n<v.foo.bar Roger #FFF #000>Hello\r\n```\r\n\r\nThe cue itself has classes \"foo\" and \"bar\", color \"\\#FFF\", background color \"\\#000\".\r\nThe `v` element has the same classes, annotation \"Roger\", same colors.\r\n\r\nTo support non-opaque colors, we can use hex annotation with 4 or 8 characters (this is supported in CSS now, per spec at least). e.g. fully transparent black is \\#0000 or \\#00000000. https://drafts.csswg.org/css-color/#hex-notation\r\n\r\nThe colors specified this way would be overridable with CSS, so it's like HTML `<font color>`, not like `style=\"...\"`."},"comment":{"url":"https://api.github.com/repos/w3c/webvtt/issues/comments/158971165","html_url":"https://github.com/w3c/webvtt/issues/272#issuecomment-158971165","issue_url":"https://api.github.com/repos/w3c/webvtt/issues/272","id":158971165,"user":{"login":"lorettaguarino","id":2747182,"avatar_url":"https://avatars.githubusercontent.com/u/2747182?v=3","gravatar_id":"","url":"https://api.github.com/users/lorettaguarino","html_url":"https://github.com/lorettaguarino","followers_url":"https://api.github.com/users/lorettaguarino/followers","following_url":"https://api.github.com/users/lorettaguarino/following{/other_user}","gists_url":"https://api.github.com/users/lorettaguarino/gists{/gist_id}","starred_url":"https://api.github.com/users/lorettaguarino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lorettaguarino/subscriptions","organizations_url":"https://api.github.com/users/lorettaguarino/orgs","repos_url":"https://api.github.com/users/lorettaguarino/repos","events_url":"https://api.github.com/users/lorettaguarino/events{/privacy}","received_events_url":"https://api.github.com/users/lorettaguarino/received_events","type":"User","site_admin":false},"created_at":"2015-11-23T15:36:28Z","updated_at":"2015-11-23T15:36:28Z","body":"I would like WebVTT to be the only caption format an author needs to\nprovide. Videos will be shown on non-browser devices like televisions where\nfull CSS support will be a heavy burden. So I think it important that we\nhave a solution to providing at least the accessibility-critical styling\nfor those UAs.\n\nOn Mon, Nov 23, 2015 at 7:11 AM, Philip Jägenstedt <notifications@github.com\n> wrote:\n\n> Is it a premise here that we care about making it easier for CSS-incapable\n> UAs to implement the spec? If it adds no burden at all for browser engines\n> that's fine, but I'm quite skeptical of adding things that only benefit\n> CSS-incapable UAs, unless the problem is severe and these UAs represent a\n> significant part of the WebVTT ecosystem.\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/w3c/webvtt/issues/272#issuecomment-158963954>.\n>\n"}}