Eric Meyer, in praise of browser prefixes such as
If the history of web standards has shown us anything, it’s that hacks will be necessary. By front-loading the hacks using vendor prefixes and enshrining them in the standards process, we can actually fix some of the potential problems with the process and possibly accelerate CSS development.
I’d add that vendor prefixes work very well with a steady diet of progressive enhancement. You, as a developer, are not bound by law to make every element on every page look exactly the same in every browser. The less tied-down each of us are, the faster all of us can move.
It bills itself as “The Most Awesome jQuery Image Slider,” and once you see it you will, if not agree entirely, see where they’re coming from.
FRMT.me is an online CSS formatter using the Extra Future house style rules, which I’ve yet to codify here but will soon. It is one of my 6-hour projects, and as such is considered a sibling to Megaman II’s Intro in HTML, CSS, and jQuery.
House style on the name is to print the domain all caps and the TLD in lowercase, like so: FRMT.me.
Great tip from Guillermo Esteves. Worked a charm on this very site.
Paul Irish’s guide to the best @font-face syntax for all compatible browsers.
Can I get a witness? Not only does it work, it works NOW.
Zeldman on a proposed webfont permissions table. This seems sort of like attaching a file to a movie that says DO NOT STEAL and expecting it to work.
Consolidates and optimizes CSS in a way which I’ve not seen before.
Which is cool, but it would be nice if it could convert it BACK so humans could read/edit it easily. Check the examples, you will be glad you did. Hey, it does do that.
A platform for css3’s @font-face. The real test of this will be how many hoops you have to jump through to embed a font, and how it handles failure:
We’ve built a technology platform that lets us to host both free and commercial fonts in a way that is incredibly fast, smoothes out differences in how browsers handle type, and offers the level of protection that type designers need without resorting to annoying and ineffective DRM.
The upside is that having a central place to access these fonts will be great for caching.
Extending Firefox with open web technologies like jQuery, HTML and CSS. I am thinking of it as the next generation of Greasemonkey.
A rare take on embedded web fonts from someone who actually makes fonts and sells them for a living. He suggests a DRM system using a “root table” that says what fonts can be used on what domains, but then says this:
There is nothing that can be done about this. All we can do is present a person with a fork in the road. The person can license the font to give the designer the respect he/she deserves for creating something that the person likes and wants to use. Or, they can ignore the Golden Rule and hack the font.
If that’s the case, and he knows it’s the case, then why not forget the DRM entirely? Why not trust people to do the right thing from the start, and call them out on it when they don’t?