I’m not entirely sure what to think of this situation, but it seems to be yet another strong piece of evidence that the people behind W3schools don’t have our best interests in mind.
I’m currently in the process of revamping my CSS3 Click Chart app and I was doing my usual cursory searches for simple JavaScript methods that I often forget the syntax for. Notice what I stumbled across, as shown in the re-enactment below.
Lately in some of my writing projects I’ve had to hunt down sources to demonstrate the importance of web page speed. Usually a quick Google search will pull up some pretty good ones, and I have a few others on file that I can refer to.
I thought I would put together a roundup of some of the ones I’ve been able to find. Web development bloggers, who are constantly promoting the importance of web page speed, should have these types of authoritative sources at their fingertips.
So consider this post the collective evidence for the importance of page speed. Posts are listed from oldest to newest.
“Vertical-align isn’t working!” cried the web developer.
The vertical-align property is one of those features of CSS that sounds pretty self-explanatory, but can cause problems for CSS beginners. I think even many CSS veterans have had problems figuring this one out at times.
In this post, I’ll try to cover it in an understandable manner.
With all the hype surrounding the new APIs and the fancy parts of CSS3, I had almost forgotten about the new reversed attribute that allows you to write a descending list of numbered items, as opposed to the default ascending list of numbered items.
You can get full details in the specification, but here I’ll summarize what it does and I’ll offer a solution for the fact that there is (from what I can see) no browser support for this attribute.
Over the last couple of weeks I’ve introduced a new link in the main navigation on this site. It’s a new section called CSS Basics.
I’ve wanted to publish info on really basic CSS stuff, because I think web design should be taught at many levels and beginners should especially be informed of the right way to do things.
If you’ve been using CSS3 transitions for some time, you might be accustomed to a certain type of syntax.
Here I’ll introduce the keyword value “all” and how it might save you a few lines of code and make things easier to maintain in the future.
The other day Paul Irish posted an article that collected together responses to a question that he and Yehuda Katz asked their Twitter folowers.
One of the wishlist items a few people mentioned was “CSS blend modes” with a use case of tinting an image on hover (or tinting it statically, then removing the tint on hover or by some other interaction). My immediate thought was: That should be simple enough, shouldn’t it?
This is a question that has been answered in a number of different places. Unfortunately, the answers in some instances have not been good ones. In fact, they’ve either been way too optimistic and/or presumptuous — or else just downright wrong.
Also, when we use the term “HTML5″, what exactly are we referring to? HTML5 covers a number of different features and technologies, some of which have nothing to do with SEO. So, generally speaking, when people ask this question, they’re usually referring to HTML5′s new semantic elements. So, I’ll primarily focus on those here.
Earlier this year, the folks at O’Reilly were kind enough to send me a review copy of Canvas Pocket Reference: Scripted Graphics for HTML5 by David Flanagan.
Admittedly, this is not a truly legitimate review because, well, I haven’t actually read the entire book. But as you can tell from the title, this is not exactly something you’d read cover to cover and get much out of. I’ve gone through some of it, and since I have no immediate plans to use HTML5′s canvas element or its related API, I probably won’t be referring to it much any time soon.
Nonetheless, there’s good reason for a positive review here.
Most good developers by now accept the fact that pixel-perfect cross-browser CSS is not only unnecessary, but also totally impossible.
Of course, when we speak of the challenge of “cross-browser” CSS, we’re really saying “How can I make this work in Internet Explorer versions 6-8?” — because those are really the most problematic browsers.
Although I’ve written before about cross-browser CSS, and I still stand by just about every word in that article, I thought I’d reiterate my feelings on this subject by providing what I feel is the best workflow for getting your CSS to be as efficient, hack-free, and maintainable as possible while providing as similar an experience in all supported browsers.