- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Sat, 30 Mar 2019 16:15:44 +0000
- To: public-css-archive@w3.org
@MatsPalmgren I'm just asking the logic to be described more clearer in the spec, because our engineers could not read the desired logic from the spec. Thanks to you and @emilio pointing to Gecko's code, I think I can understand that. I also looked at WebKit's, which looks a bit different from Gecko's. I'm fine with whichever options, or with the one @frivoal proposed, or with something else. My request is just to describe the logic more clearer to the spec so that we can implement. Did this explain better? To explain our problem better, we were reading the [Resolved Values spec](https://drafts.csswg.org/cssom/#resolved-values), which says "The resolved value is the used value" for the `line-height` property. The [Used Values spec](https://drafts.csswg.org/css-cascade-4/#used-value) says: > The used value is the result of taking the computed value and completing any remaining calculations to make it the absolute theoretical value used in the layout of the document. If the property does not apply to this element, then the element has no used value for that property. We could not read this paragraph to the logic you quoted, hence asking better clarification in the spec. -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3749#issuecomment-478260656 using your GitHub account
Received on Saturday, 30 March 2019 16:15:51 UTC