Christopher Finke

I’m not able to reproduce that bug; what version of WordPress are you running? What URL do you see the error on?

Thanks; we appreciate your help.

Not at the moment. We’ll look at adding a way to target just the mobile theme with custom CSS in the next release.

Thanks for the report; we’ll get it fixed as soon as possible.

I’m not able to reproduce this error; are you using any plugins other than Jetpack? What version of Clear Line are you using?

Less than 24 hours. Doing some more testing to make sure we didn’t overlook anything else.

A fix has been committed and will be included in a forthcoming bugfix release.

A fix has been committed and will be included in a forthcoming bugfix release. For now, remove the Top Posts widget until the upgrade is available.

I can reproduce the error as well; I’m looking into it.

I can duplicate the problem; I’m looking into it now.

There’s no Trac ticket, but I do know what’s causing the src: line to get stripped. Some of the security filters for WordPress.com got left in Custom CSS when it was ported to Jetpack; I’ll strip those out for the next release.

That makes sense, as the bug was in some code that condenses CSS by eliminating multiple definitions of CSS properties so that code like this:

body {
  width: 100px;
  color: green;
}

body {
  font-weight: bold;
  color: red;
}

body {
  text-decoration: underline;
  color: orange;
}

turns into this:

body {
  width: 100px;
  font-weight: bold;
  text-decoration: underline;
  color: orange;
}

There are a few properties that are allowed to be defined multiple times, but transition (and -webkit-transition) were erroneously left out of that list.

I’ve fixed the problem with -webkit-transition for the next release as well.

(1) I tried commenting out a section of code that I thought I would use later. When I clicked “Save Stylesheet”, the comment disappeared, and my work was lost.

Comments getting stripped out is a known issue; it’s on our list of things to fix.

(2) I tried using -webkit-filter, which worked fine in the theme’s stylesheet. When I saved, however, it was deleted. I don’t know why Jetpack would delete perfectly valid code.

You’re right; it shouldn’t have been stripped out. We’ll have it fixed in the next release.

Sigh, had to push 1.4.3 to really fix it all.