- From: David Singer <singer@apple.com>
- Date: Wed, 19 Jun 2019 13:54:03 +0200
- To: Silvia Pfieffer <silviapfeiffer1@gmail.com>
- Cc: Glenn Adams <glenn@skynav.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Philippe Le Hegaret <plh@w3.org>, Pierre-Anthony Lemieux <pal@sandflow.com>, Gary Katsevman <me@gkatsev.com>, Cyril Concolato <cconcolato@netflix.com>, Public TTWG List <public-tt@w3.org>
> On Jun 19, 2019, at 13:43 , Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > > > > On Wed., 19 Jun. 2019, 5:46 pm David Singer, <singer@apple.com> wrote: > > > > On Jun 19, 2019, at 9:33 , Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > > > > > > > > On Wed., 19 Jun. 2019, 1:45 pm Glenn Adams, <glenn@skynav.com> wrote: > > > > > > On Tue, Jun 18, 2019 at 6:02 PM Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > > On Tue, Jun 18, 2019 at 10:32 PM David Singer <singer@apple.com> wrote: > > > > > > > > > > > > > On Jun 18, 2019, at 14:19 , Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > > > > > > > > > > > > > > > > While I agree with this and also have no problem excluding this from REC, is still like to encourage the CSS WG to continue with it. Glenn's listing of existing deterministic algorithms in this space should be enough to give us an expectation that it's feasible and technically possible. > > > > > > I’ve heard offline that people think that there are reasonable algorithms too. That doesn’t make it specifiiable yet, tho. > > > > I don't follow: if it's been implemented and made replicable, it can > > be specified. > > > > Just because some algorithm can be specified doesn't mean it will be specified in a form that permits a normative reference, particularly in a reasonable amount of time. Are you willing to wait for 2 or 3 years to elapse to get an algorithm written into a CSS spec, get it tested, and move that spec to at least PR or REC before moving forward on VTT? > > > > We can wait if there's progress (not with REC, but we don't need it for REC). > > we can’t go to Rec with the default being something that’s underspecified and unimplemented, and we are way past needing to go to Rec. > > > Why would a missing balancing algorithm stop us from going to REC? Because there is a mandate that it’s the default: • the text-wrap property must be set to balance [CSS-TEXT-4] > It's not like the text can't be rendered in the traditional CSS fashion, which is what browsers do currently. It doesn’t actually say that everyone has to *support* balance, though that’s implied. I suppose we could insert normative text to say that when the text-wrap property is ‘balance’, UAs may simply wrap. David Singer Manager, Software Standards, Apple Inc.
Received on Wednesday, 19 June 2019 11:54:38 UTC