removing fallback behavior

CSL Development
1

I’ve raised this once before, but want to raise it again:

I think we should remove the language in the spec about fallback
behavior on types.

Reason:

  1. it’s unnecessary when we have the conditional support (which didn’t
    exist when I created this feature)

  2. it adds unnecessary complexity to implementations

  3. it adds some black magic that can result in unexpected behavior for
    style authors

  4. as I’ve been saying for the past many years, types are overrated as
    mechanisms to get correct formatting

So let’s ditch it.

Bruce

2

I’ve raised this once before, but want to raise it again:

I think we should remove the language in the spec about fallback
behavior on types.

Reason:

  1. it’s unnecessary when we have the conditional support (which didn’t
    exist when I created this feature)

  2. it adds unnecessary complexity to implementations

  3. it adds some black magic that can result in unexpected behavior for
    style authors

  4. as I’ve been saying for the past many years, types are overrated as
    mechanisms to get correct formatting

So let’s ditch it.

No objections! (I confess that I didn’t even know that fallback on
types was required, so this is all good news.)