Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365)

I don't think the computed value spec sentence "For <length> the absolute value, otherwise a percentage." is what it should be, we should simply have similar wording to other `<length-percentage>` properties, e.g. "a computed `<length-percentage>` value"

The specific Chrome bug about calc(0% + 10px) isn't specific to this property.

The custom behavior for offset-distance (e.g. wrap around if we have a closed path) occurs when using the value.


-- 
GitHub Notification of comment by ewilligers
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/365#issuecomment-526486650 using your GitHub account

Received on Friday, 30 August 2019 07:09:50 UTC