C:\ Home » 2012 (Page 5)

I Decided To Skip The CSS Reset

CSS Resets have been growing in popularity over the years, until it's become such a standard that many tutorials guiding you through the basics of CSS even advice you to include a CSS Reset, before you do anything else! No doubt it can be useful to bridge the differences in the way browsers display different elements, but at the same time there are a few cons to this useful technique.

The big one, is that every element added to your stylesheet is a request to the browser. The more styles you include, the heavier your site will be to load. Not like it will be a noticable difference for most sites; especially not if you're using a modern computer and browser, but in the service of tweaking webpages as much as possible, styles that aren't necessary to add shouldn't be added. For example, I never use the <cite> tag, so there's no reason why I should include it in my stylesheet.

The CSS Reset I used last year had a lot of unnecessary elements in it, and a lot of necessary ones, too. When I implemented it some of the elements I had styled myself suddenly looked a bit messed up due to browser-defined margins and paddings and other things suddenly receiving a null value, so I had to redo quite a bit of code with the new values in mind. But considering I'm getting a display standard not based on a specific browser, it was worth the time it took to change.

But a CSS Reset won't fix everything. I realized while going through my stylesheet that everything I'd like to tweak doesn't need a Reset. The Reset is for the most part just a duplicate value of something I'm styling myself, and the browser doesn't interfere as much as you'd think. Since IE implemented the quotation marks for <q> tags, there aren't so many noticeable differences between them either.

It might require me to check the site on different browsers once in a while and look for bugs, but otherwise, the switch will make things both easier and faster. So, I'm skipping the reset this time around.

No Hover On Visisted Links!

I stumbled upon a noobish problem today. While messing around with the site CSS I decided to add values for visited and active links, and I added them after the values for link and hover. That's a no go! As it turns out, the visited link color will be applied to both visited links as they are, and to visited links when you try to hover over them. The correct order or link values is this (along with a sneakpeak snippet of next years theme):





It's worth a post! :)

How To Test A Theme Before Making It Public

Use this. I'mma get to work on the 2013 version right about now, but this time, you won't see it before it's done. ;)


Might as well post this post.

Testing Compression Time

If you want to zip with 7... get a fast computer. :)

Testing Compression Time

Active X Is History

Remember Active X? The Microsoft Framework developed back before the millennium switch? Maybe you remember that message that used to pop up at the top of the browser asking you to install some kind of extension to enable use of some kind of feature which at the same time allowed potential hackers to run amok on your system? It turns out Active X support disappeared for Firefox back in 2008, with the release of FF 2. IE still supports it. I read a recent post about how it's not time to celebrate it's earthly departure yet, it's still in use, but it's like a remnant of a past that there's no longer reason to remember. Active X Is History.

Privacy   Copyright   Sitemap   Statistics   RSS Feed   Valid XHTML   Valid CSS   Standards

© 2022
Keeping the world since 2004.