-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joint TTWG and CSS WG meeting at TPAC 2019 #52
Comments
Add to the list: |
For WebVTT, we had questions whether we could call vendor prefixes as implemented/implementable for the IR. It would be good to get input from the CSS WG in regard to whether a vendor-prefixed property could be considered acceptable. |
The Timed Text Working Group just discussed The full IRC log of that discussion<cyril> Topic: Discussion points for CSS WG at TPAC 2019 #52<cyril> github: https://github.com//issues/52 <cyril> nigel: the list as it stands has a bunch of CSS issues and one TTML one at the moment <cyril> ... the TTML one is about text-combine <cyril> ... then shearing <cyril> ... then equivalent of multiRowAlign <cyril> ... then about background area with fillLineGap <cyril> ... and for that one there is a proposed solution <cyril> ... then padding at start and end of line <cyril> ... but the issue is closed <cyril> ... and last one is images with layout information, like Apple Pay logo <cyril> ... I think there is another one about accessibility <cyril> ... there is a CSS WG issue which concerns making something invisible on a visual presentation but visible to screen readers <cyril> ... there seem to be quite a few requirement on this <cyril> ... CSS WG issue 560 <nigel> -> https://github.com/w3c/csswg-drafts/issues/560 [css-display] create a display property value for visually hiding an element while making it available for AT #560 <cyril> ... and that is connected to an IMSC issue that I raised recently <cyril> ... to expose burned-in narrative text to a screen reader <cyril> ... sighted people can see it but we want to put that in a ARIA live region <cyril> rrsagent, pointer <RRSAgent> See https://www.w3.org/2019/09/05-tt-irc#T15-02-25 <nigel> rrsagent, make minutes <RRSAgent> I have made the request to generate https://www.w3.org/2019/09/05-tt-minutes.html nigel <nigel> Regrets- Glenn <nigel> Regrets+ Glenn_first_hour <cyril> pal: we also issue 44 from IMSC <cyril> nigel: it is in the GitHub list <cyril> nigel: about TPAC planning, I have an email from Alan, one of the CSS WG chairs <cyril> ... proposing at 9:30 on Tuesday morning <cyril> ... I'm going to say yes <cyril> nigel: regarding the M&E IG, they listed 2 topics <cyril> ... but there are lot more topics we could talk about <cyril> ... live, karaoke, danmaku, ... <cyril> ... and we could think about MSE and text tracks <cyril> ... because MSE only supports audio/video <cyril> ... those are my suggestions <cyril> ... but we have a limited amount of time <cyril> ... are there other topics or prioritization views? <cyril> cyril: when will the new text track api be discussed <nigel> -> https://www.w3.org/2011/webtv/wiki/Face_to_face_meeting_during_TPAC_2019#16:00_-_17:00_Timed_Text_Working_Group_joint_meeting M&E IG agenda <cyril> pal: on wednesday <cyril> nigel: there is a request for break out sessions and a request for demo <cyril> ... do we want to raise the text track api with the M&E IG? <cyril> cyril: no <cyril> gkatsev: we need to check what is the overlap between the M&E IG, the Media WG and the TTWG <cyril> nigel: that's exactly the sort of thing that the M&E IG should discuss, I'll ping Chris |
Closing since this relates to 2019's TPAC joint meeting, which definitely happened. |
Schedule and location
Date: Tuesday 17th September 2019
Time: 0930-1030
Place: Room allocated to the CSS WG
Topics
These topics are collated from the comments on the issue.
The text was updated successfully, but these errors were encountered: