Re: [csswg-drafts] [css-env] Adding custom env() variables

• From: Tommy Hodgins via GitHub <sysbot+gh@w3.org>
• Date: Mon, 07 May 2018 15:34:36 +0000
• To: public-css-archive@w3.org
• Message-ID: <issue_comment.created-387104752-1525707275-sysbot+gh@w3.org>

What would the advantage of 'custom `env()` variables' be compared to using the CSS custom properties we already have?

These `env()` values could potentially be things the browser user has influenced (like if they have a setting for 'prefer low motion' or 'high contrast' that gets exposed as an `env()`, or information about the device, OS, and browser it's being displayed in) but if they're settable by CSS authors that seems like it defeats the purpose of them—if it's the case that we want custom settable variables _and_ special variables with reserved names that the browser supplies to value to why not expose these values as some kind of reserved default CSS custom property, what would we even need `env()` for?

-- 
GitHub Notification of comment by tomhodgins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2627#issuecomment-387104752 using your GitHub account

Received on Monday, 7 May 2018 15:34:40 UTC