Florian Rivoal
Florian Rivoal
@xfq In that case, either W3C should not retire tr.rdf until find the time/money to do the work to integrate the new API (which possibly includes improving the new API,...
Check the spec, and if updates discussed in Paris have been applied.
Yes, the resolution I was thinking about has been applied (it's commit https://github.com/w3c/csswg-drafts/commit/7b5d13351c9408f587ecf86ddcab714d043c4fa8). This means the quote from the spec above is no longer correct. The new correct is: >...
Note that flex fragmentation is under specified, as the spec only gives some details about what should happen, but leaves important questions open, and merely suggests (rather than mandate) an...
Also see this conversation: https://github.com/vivliostyle/vivliostyle-formatter-issues/issues/19
I think this issue: https://drafts.csswg.org/css-text-4/#issue-078e398a is actually unimportant, and we can pick anything we like. having different fonts for the character we're trying to allign is an error case, not...
I would have expected browsers to already agree on this. Interesting that they don't. Which part of the CSS Syntax spec makes you think this is the correct behavior? I...
The rule was designed so that unknow stuff gets ignored and the parser falls back on its feets as soon as possible, **but** we need `[ ]` and `( )`...
Yes, that one needs to make the second rule apply.
I did not know how the code is structured, but I suspected that might be the case. Even then, I think it is more important to fix vivliostyle/vivliostyle.js#95, even if...