CSS3 and CSSOM

[kriskowal]

CSSOM does not round-trip syntax it does not recognize, like gradients.

[Stuk]

As in, it strips them out?

[kriskowal]

Yes. The parser does not recognize them so it does not produce a node in the syntax tree. The information is lost before rewriting.

[kriskowal]

This appears to be related to NV/CSSOM#16, which is open at time of this writing.

[ralyodio]

I'm also having problem with css gradients being stripped out because of vendor prefixes/multiple definitions issue.

[Stuk]

The latest version of Mop has disabled CSS compression because of this issue. Are you using the latest version?

[ralyodio]

I would assume so. I just installed juice yesterday.

[Stuk]

And Mop is still stripping out your CSS gradients?

[ralyodio]

Yes, if I define two background properties, only the last one shows up.

[Stuk]

My mistake, I was looking at some local changes. I've pushed v0.12.4 to npm which doesn't compress CSS by default. Would you mind trying again to see if this fixes your problem? Many apologies!

[ralyodio]

I just installed juice, which should have eventually pulled in your package and it still is ignoring multiple background properties. Only the last one shows up.

[Stuk]

What do you mean by "juice"?

[ralyodio]

npm install juice

its the package that depends on your package at least directly or indirectly. I'm using it to convert css to inline css.
https://github.com/LearnBoost/juice

[Stuk]

Both Mop and Juice depend on CSSOM, which is where the bug is. Mop (this project) is a different tool. You'll need to comment on this bug: NV/CSSOM#16 to make your problems known.

[kriskowal]

└─┬ [email protected]
  ├── [email protected]
  ├─┬ [email protected]
  │ └── [email protected]
  ├── [email protected]
  ├─┬ [email protected]
  │ ├─┬ [email protected]
  │ │ └── [email protected]
  │ ├── [email protected]
  │ ├── [email protected]
  │ ├── [email protected]
  │ └─┬ [email protected]
  │   ├─┬ [email protected]
  │   │ ├── [email protected]
  │   │ └─┬ [email protected]
  │   │   └── [email protected]
  │   └── [email protected]
  ├── [email protected]
  └─┬ [email protected]
    ├── [email protected]
    ├── [email protected]
    ├── [email protected]
    ├── [email protected]
    ├── [email protected]
    └── [email protected]

[ralyodio]

Oh, I thought this fixed the compressing bug for CSSOM.
How is your code working around it?

On Fri, Feb 15, 2013 at 11:50 AM, Kris Kowal [email protected]:

└─┬ [email protected]
├── [email protected]
├─┬ [email protected]
│ └── [email protected]
├── [email protected]
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └─┬ [email protected]
│ ├─┬ [email protected]
│ │ ├── [email protected]
│ │ └─┬ [email protected]
│ │ └── [email protected]
│ └── [email protected]
├── [email protected]
└─┬ [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-13624654.

Anthony Ettinger
http://anthony.ettinger.name
[email protected]
+1 (831) 406-1123

[kriskowal]

We have turned off CSS optimizations in Mop until such a time as CSSOM
fixes the problem or an alternate CSS object model that can round-trip
arbitrary CSS is created to replace it.

[Stuk]

We're just not compressing CSS for the moment :)

[Stuk]

This can be closed with gh-19