- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 12 Sep 2012 12:31:31 -0700
- To: Brian Kardell <bkardell@gmail.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
On Wed, Sep 12, 2012 at 11:24 AM, Brian Kardell <bkardell@gmail.com> wrote:
> While trying to figure out some incredibly perplexing treatment of some
> inline <style> rules in ie7 I did a search and accidentally came across
> this:
>
> http://msdn.microsoft.com/en-us/library/bb250496(v=vs.85).aspx
>
> Which uses the verbiage "custom properties" ....
>
> """
> _ Underscore Filter
> This CSS filter is based on a parser bug. It used to show properties
> exclusive to Internet Explorer. These constructs will now be treated as a
> "custom property" by Internet Explorer 7 and later. Custom property means
> that it is still in the OM and can be queried through script but does not
> natively apply its value.
> /* The following rule used to apply min-height
> to browser who understand this property and
> height to IE. In IE7, _height will be treated
> as a custom property (no height will be applied) */
>
> .myclass {
> min-height: 300px;
> _height: 300px;
> ...
> }
> """
>
> Is that a good thing or a bad thing (or maybe doesn't matter) for css
> variables/custom properties?
I don't see how it impacts vars at all. It's just a convergent use of
naming in a relatively unimportant place.
~TJ
Received on Wednesday, 12 September 2012 19:32:18 UTC