[TTWG] CR update for WebVTT

[himorin]

Link to group's decision to request transition

After CfC for PR ended without resolution, it seems we have agreement after decision on direction. Is it suitable to point an agreement on this?

Link to previous Candidate Recommendation transition request

#126

Substantive changes

• issue 457, PR 461: Make VTTRegion lines be a long
• issue 467, PR 470: Update region lines parsing to round to ± MAX_VALUE

Marking followings as at-risk:

• text-wrap: balance (issue 455)
• text-combine-upright (issue 456)
• line alignment
• position alignment

Diff: https://github.com/gkatsev/webvtt/blob/at-risk-june/archives/2019-09-01/diff.html

Any changes in normative references?

No change

Any changes in requirements?

No change

Wide Review of substantive changes

Substantive changes didn't impact reviews

Issues status

https://github.com/w3c/webvtt/issues

Formal Objections

None

Any changes in implementation information?

Implementation report updated: https://www.w3.org/wiki/TimedText/WebVTT_Implementation_Report
Every one of the failing tests is a browser implementation bug and is fixable. None of these
mean that the spec isn't implementable (as in [5]).

*5 http://lists.w3.org/Archives/Public/public-tt/2019Jun/0003.html
*6 https://lists.w3.org/Archives/Public/public-tt/2019Jun/0033.html

Deadline for further comments

(publication date + 4 weeks)

Any changes in patent disclosures?

None
https://www.w3.org/2004/01/pp-impl/34314/status

(as draft for now; cc @plehegar , @gkatsev )

[nigelmegitt]

@himorin Your link to agreement is to an agreement to merge a pull request, not to publish a CR.

[swickr]

I'm not convinced this was yet ready for Director review. #460 hasn't been merged so the four issues haven't yet been closed.

[gkatsev]

Yeah, I think this can be closed? @himorin opened this at my behest but there was a misunderstanding on my end about whether the pull request itself was ready vs it being ready to proceed to another CR.

[himorin]

I'm not convinced this was yet ready for Director review. #460 hasn't been merged so the four issues haven't yet been closed.

Yeah, I think this can be closed? @himorin opened this at my behest but there was a misunderstanding on my end about whether the pull request itself was ready vs it being ready to proceed to another CR.

I can close this for now, actually I was told to open issue with draft request for editing without awaiting director label by @plehegar ...

[plehegar]

closing this for now but could be re-opened later.