- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Aug 2021 03:54:56 +0000
- To: public-css-archive@w3.org
In general, I agree with @emilio, and we should have fragment-aware APIs to properly investigate fragment specific questions, and return something simple here, since we cannot do it perfectly anyway. But we might not be able to return the value of the first fragment in all cases, due to compat concerns. For instance, I suspect (though I don't know for sure) that for padding-bottom, there might be an expectation to return the value of the last fragment, not the first one. But this would have to be investigated on a property by property basis. How about we spec that the value returned should be based on the first fragment, except in explicitly listed cases where we define exactly what happens, and we add to that list as we discover good reasons to make exceptions. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6513#issuecomment-906072628 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 August 2021 03:54:58 UTC