All issues

Search results

Clarify that '' and "" are invalid <family-name>

Status: Open.

#1285 In w3c/ttml2;

· palemieux opened on Jul 27, 2026

LWSP pruning within elements with non-mixed type content models

Status: Open.

#1284 In w3c/ttml2;

· palemieux opened on Apr 21, 2026

tts:zIndex wording seems backwards

Status: Open.

#1279 In w3c/ttml2;

· icbaker opened on Feb 25, 2025

Paint-on example is broken

Status: Open.

#1268 In w3c/ttml2;

· cconcolato opened on Oct 12, 2023

Incorrect usage of forward/backward compatibility in Sections 3.4.[12]

editorial

Status: Open.

#1267 In w3c/ttml2;

· skynavga opened on Jul 25, 2023

Allow markup in metadata element contents, e.g. for direction

Status: Open.

#1266 In w3c/ttml2;

· nigelmegitt opened on Jul 24, 2023

Missing closing bracket in XML Representation?

editorial

question

Status: Open.

#1264 In w3c/ttml2;

· himorin opened on Apr 18, 2023

Reporting a vulnerability

Status: Open.

#1263 In w3c/ttml2;

· igibek opened on Apr 10, 2023

No feature to indicate TTML2 profile attribute vocabulary _only_

enhancement

Status: Open.

#1261 In w3c/ttml2;

· nigelmegitt opened on Dec 20, 2022

Define ttm:role values solely via the role registry

agenda

Status: Open.

#1248 In w3c/ttml2;

· nigelmegitt opened on Sep 14, 2022

Clarify version negotiation or lack thereof

privacy-trackerGroup bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

Status: Open.

#1246 In w3c/ttml2;

· samuelweiler opened on Apr 4, 2022

Clarify "the first font obtained" in tts:lineHeight normal algorithm.

editorial

Status: Open.

#1241 In w3c/ttml2;

· skynavga opened on Aug 5, 2021

·  

2ED-PR