Tag: css

Getting the “Belle & Sebastian effect” with CSS filters

There are a lot of articles out there regarding using SVG’s feColorMatrix with CSS filters to get a “duotone” or “Instagram” effect on photos, but frankly most of the examples looked too weird to me, and the matrix multiplication that’s going on is pretty hard to wrap my brain around.

Usually what I want is a simple monochrome duotone effect; in other words, the Belle & Sebastian effect:

Most of these are a “dark” duotone effect, where the blacks remain black and the whites become the desired color.

Continue reading “Getting the “Belle & Sebastian effect” with CSS filters”

Leave a Comment

Chris Coyier on PostCSS

Chris Coyier on PostCSS:

We know that specs change. It happens all the time. Seems weird to base a syntax on a non-final spec. What happens when the spec changes? Do you change the language and let existing code break? How is that future-proof? Or support all past formats? Meaning the language isn’t really based on future CSS, it’s based on any experimental idea that was considered?

These have been exactly my thoughts since hearing about CSS post-processors. How can people honestly believe that the code they’re writing is future-proof? Sass source files certainly are prone to “spec rot”, but the CSS they generate isn’t (at least, insofar as anything can be immune to it).

On writing real CSS (again) | CSS-Tricks

One Response

Opera Border Radius in 2010?

Opera has been maybe the most standards-conscious browser over its lifetime. This has resulted in frustration among users, who believe it to be “broken” because it doesn’t render lazy code correctly — code that takes advantage of the forgiveness of other browsers, allowing you to write sloppily and get away with it.

But it has also resulted in frustration among web developers, who are impatient at Opera’s reluctance to adopt any standards that haven’t been laser-etched into platinum tablets down in the W3C’s basement foundry. Among them is the border-radius property, an effect that will probably be out of vogue anyway by the time Opera’s Presto engine implements it. Of course, since CSS3 has been kicked around the W3C offices since 1999, and border-radius itself since 2001, most other engines (Gecko, WebKit, KHTML) stopped waiting and began inventing their own properties for this effect. Presto has not.

In the course of reminding myself of this lamentable fact by searching for workarounds today, I noticed that some Opera developers are casually dropping hints that the full-blown, unqualified, W3C-crafted border-radius itself has made an appearance in Presto 2.3, and that the next version of Opera will be powered by 2.4.

It’s all true, I saw it on Twitter.

3 Responses