- From: Alice via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Sep 2019 04:13:11 +0000
- To: public-houdini-archive@w3.org
alice has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-properties-values-api] Rationale for `registerProperty()` taking precedence over `@property`? == Coming here from https://github.com/w3ctag/design-reviews/issues/402 (thanks @andruud for the helpful links to controversial closed issues!) In #845, @tabatkins wrote > registerProperty() wins over @Property rules I'm curious what the rationale is, since it doesn't seem to be documented in that issue. Also, in that issue, via #902, there seemed to be consensus that: > ... they're independent (that is, you can't unregisterProperty a property registered via @Property, and vice-versa, and then you just need to specify in which order do we look at the two sets if there's a name conflict). That doesn't seem to be reflected in the spec, which explicitly states > Valid `@property` rules result in a registered custom property, as if `registerProperty()` had been called with equivalent parameters. Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/943 using your GitHub account
Received on Tuesday, 10 September 2019 04:13:12 UTC