Tag: css

Getting the “Belle & Sebastian effect” with CSS filters

There are a lot of arti­cles out there regard­ing using SVG’s feColorMatrix with CSS fil­ters to get a “duo­tone” or “Insta­gram” effect on pho­tos, but frankly most of the exam­ples looked too weird to me, and the matrix mul­ti­pli­ca­tion that’s going on is pret­ty hard to wrap my brain around.

Usu­al­ly what I want is a sim­ple mono­chrome duo­tone effect; in oth­er words, the Belle & Sebas­t­ian effect:

Most of these are a “dark” duo­tone effect, where the blacks remain black and the whites become the desired col­or.

Con­tin­ue →

Chris Coyi­er on PostC­SS:

We know that specs change. It hap­pens all the time. Seems weird to base a syn­tax on a non-final spec. What hap­pens when the spec changes? Do you change the lan­guage and let exist­ing code break? How is that future-proof? Or sup­port all past for­mats? Mean­ing the lan­guage isn’t real­ly based on future CSS, it’s based on any exper­i­men­tal idea that was con­sid­ered?

These have been exact­ly my thoughts since hear­ing about CSS post-proces­sors. How can peo­ple hon­est­ly believe that the code they’re writ­ing is future-proof? Sass source files cer­tain­ly are prone to “spec rot”, but the CSS they gen­er­ate isn’t (at least, inso­far as any­thing can be immune to it).

On writ­ing real CSS (again) | CSS-Tricks

Opera Border Radius in 2010?

Opera has been maybe the most stan­dards-con­scious brows­er over its life­time. This has result­ed in frus­tra­tion among users, who believe it to be “bro­ken” because it does­n’t ren­der lazy code cor­rect­ly — code that takes advan­tage of the for­give­ness of oth­er browsers, allow­ing you to write slop­pi­ly and get away with it.

But it has also result­ed in frus­tra­tion among web devel­op­ers, who are impa­tient at Oper­a’s reluc­tance to adopt any stan­dards that haven’t been laser-etched into plat­inum tablets down in the W3C’s base­ment foundry. Among them is the bor­der-radius prop­er­ty, an effect that will prob­a­bly be out of vogue any­way by the time Oper­a’s Presto engine imple­ments it. Of course, since CSS3 has been kicked around the W3C offices since 1999, and bor­der-radius itself since 2001, most oth­er engines (Gecko, WebKit, KHTML) stopped wait­ing and began invent­ing their own prop­er­ties for this effect. Presto has not.

In the course of remind­ing myself of this lam­en­ta­ble fact by search­ing for workarounds today, I noticed that some Opera devel­op­ers are casu­al­ly drop­ping hints that the full-blown, unqual­i­fied, W3C-craft­ed bor­der-radius itself has made an appear­ance in Presto 2.3, and that the next ver­sion of Opera will be pow­ered by 2.4.

It’s all true, I saw it on Twit­ter.