Re: [css-houdini-drafts] [css-typed-om] Will need to handle min()/max()

I'm definitely going for that last one (separate interfaces per operator).  It works better in general, and it's more future-proof; right now all our calc() operators take either 1 argument, or N identically-handled arguments, but it's possible we may add operators in the future that take, say, 2 arguments that are interpreted differently. (For example, a round() function.)  In that case, it's better to have an interface that reflects the two arguments properly, as separate attributes.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/359#issuecomment-300253431 using your GitHub account

Received on Tuesday, 9 May 2017 18:08:22 UTC