You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Excess parenthesis in text layout algorithm? ("Position on path" part) #382
In the "11.5. Text layout – Algorithm" [1], step 8.5.1.2.4, which reads:
Let offset be the value of the ‘textPath’ element's ‘startOffset’ attribute, adjusted due to any ‘pathLength’ attribute on the referenced element (if the referenced element is a ‘path’ element).
there's an additional restriction placed on when 'pathLength' applies ("if the referenced element is a ‘path’ element"). This restrictions seems to stem from the initial landing of the text layout algorithm. However (IIRC), since then all the basic shape elements gained 'pathLength' powers. Maybe this restriction (parenthesis) should be dropped?
Yes, the parenthesis and text within should be dropped.
A test of Firefox and Chrome shows that they have implemented 'pathLength' on shapes (tested with 'stroke-dasharray' in both and also with 'startOffset' in Firefox 62).
Activity
boggydigital commentedon Jun 11, 2018
Not blocking updated 2.0 CR publication - assigning 2.0 Recommendation milestone to clean this up before 2.0 REC
Tavmjong commentedon Jun 28, 2018
Yes, the parenthesis and text within should be dropped.
A test of Firefox and Chrome shows that they have implemented 'pathLength' on shapes (tested with 'stroke-dasharray' in both and also with 'startOffset' in Firefox 62).
Remove unintended restriction that 'pathLength' only applied to paths…
Tavmjong commentedon Jun 28, 2018
Tests: web-platform-tests/wpt#11712
Spec: #476
Remove unintended restriction that 'pathLength' only applied to paths…