Skip to content

[css-properties-values-api] Allowing a default invalid initialValue when syntax is not "*" #453

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jyc opened this issue Aug 21, 2017 · 2 comments

Comments

@jyc
Copy link
Contributor

jyc commented Aug 21, 2017

Right now, we allow a default invalid initial value when syntax is omitted or is "*" (discussed in #286). While writing testcases/demos for the Servo implementation, I actually expected the same to apply when the syntax was specified to be something other than "*", because I normally only used typed custom properties on specific elements, e.g. for animation and felt kind of icky giving an initial value to everything on the page, and also because unregistered custom properties work that way.

Tab pointed out some problems, in particular, that the value you'd get back for the computed value might not always be an actual value of that type anyomre (it'd be null or ""), and that it would most likely be an authoring error.

Overall, though, it seems to me like it would be more natural and more similar to unregistered custom properties to allow a default invalid initial value for all syntaxes.

@css-meeting-bot
Copy link
Member

The Working Group just discussed Allowing a default invalid initialValue when syntax is not "*", and agreed to the following resolutions:

  • RESOLVED: Reject as no change.
The full IRC log of that discussion <nainar> Topic: Allowing a default invalid initialValue when syntax is not "*"
<nainar> GitHub: https://github.com//issues/453
<nainar> TabAtkins: Syntx of custom props is *. This allows default invalid value too.
<nainar> TabAtkins: Servo iplementor expected default invalid value to be allowed too. But I think no, you should declted an initial value
<nainar> TabAtkins: I dont see why we should allow a bottom value to all properties like this.
<nainar> TabAtkins: Proposal reject as no change?
<nainar> astearns: if yu had alot of registere props of a particulat type. Make sure initial value is in every declaration.
<nainar> TabAtkins: This is already required.
<nainar> iank_: It's trivial to do this
<nainar> RESOLVED: Reject as no change.
<TabAtkins> ScribeNick: TabAtkins

@nainar
Copy link
Contributor

nainar commented Jan 4, 2018

Closing this issue as a WontFix as per the Resolution

@nainar nainar closed this as completed Jan 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants