Minutes Sophia-Antipolis F2F Part IV 2014-09-09: Initial Letters, Animations
Initial Letters
- Resolved: Publish FPWD of CSS-inline with
initial-letter
section intact, and 2 prior sections pointing to appropriate parts of 2.1, with note that they will be updated.
- Resolved:
initial-letter
depends on line grid spacing or (if none) line-height of containing block. Does not depend on content of the lines.
- Resolved:
initial-letter
does not have longhands
- Resolved: Order of values is size first, drop second (as decided in previous F2F)
- Resolved: Size is a
number
. Alignment point is determined by script.
- There were some unresolved concerns about the best approach to handle initial letters with combining marks.
- Discussed cases where the alignment subject should be the glyph bounds vs. the margin-box bounds.
- Ruby’s interaction with
initial-letter
was also an area of concern.
Full Minutes || Spec Referenced
Animations
- sgalineau outlined the remaining issue about how to resolve properties that depend on a value from a different property. The options for the behavior were outlined in an e-mail from dbaron available here
- All the options were evaluated and the group originally leaned toward option D.
- There was a lot of testing done to determine which behavior browsers currently use and there was no clear winner.
- Eventually it was concluded that the optimal behavior was option G (Base values are interpolated values from all animations on this element and on all elements on which its computed values depend) with the beta variant (Base values are dynamic (i.e., if the expected value at a future time changes the running animation changes to match)).
- Resolved: Use Option G Beta
- Resolved: Animations and Transitions both really do have the behavior that non-interpolable properties switch at 50% of the timing function.
- TabAtkins will write an e-mail summarizing the proposal phasing out current requirements for snapshotting some events.
- Resolved: When
animation-duration:0s
, start/end events fire with 0 elapsedTime
- Resolved: Iteration events only fire for iterations that are actually run e.g. those not ‘absorbed’ by a negative delay.
- Pause events were discussed and had a lot of interest, but were deferred to level 2 in order not to delay Animations level 1.
Full Minutes || Spec Referenced
« Previous article
Next article »