Tag Archive: CSS


Is your CSS easy for another person to deal with? If they want to add a new element to the design, would they find it easy to build on your work, or would they have to create brand new class or ID declarations for each addition?

I’m sure we can all agree that none of these outcomes are much fun, and the less painful it is to deal with someone else’s CSS, the better. So let’s see how Object Oriented CSS have benefits on your project.

Object Oriented CSS isn’t really a framework … but a way of writing scalable, sane, maintainable CSS.Object Oriented CSS (OOCSS) is making a mental shift towards easy maintenance and reuse of your styles, even if it means writing extra HTML markup.

Object Oriented CSS methodologies help you to look beyond your immediate design goals and organize your code so that adding new site content that reuses the same styles in the future becomes trivial. With OOCSS, adding a new type of page to your site should mean that there’s no need to create additional CSS styles or selectors. New page types should be able to reuse existing CSS styles as much as possible. Continue reading

Advertisements

If you are one of those meticulous types who like to follow rules, it
would be better that you do not use the css scrollbar properties. Decorating the scrollbar is possible only in IE browser. You can set colors for all these on a scrollbar using styles. And here are the CSS properties that govern these colors

html {scrollbar-face-color: #FF0000;
scrollbar-shadow-color: #0000FF;
scrollbar-highlight-color: #00FF00;
scrollbar-3dlight-color: #FF00FF;
scrollbar-darkshadow-color: #00FFFF;
scrollbar-track-color: #FFFF00;
scrollbar-arrow-color: #000000;}

Cascading Style Sheets (CSS) makes easy to the web designer and developer . Because CSS can be import form a different files makes easy to control whole web site through CSS. Cascading Style Sheets reduce many unnecessary HTML tags. So lets discuss about more information about Cascading Style Sheets.

Below I am going to break out each one of the parts of CSS and explain them in non-techie terms:

  1. Selector
  2. Property
  3. Value

This is what these three parts will look like when they are all put to together:

selector { property: value }
#wrapper {display:block}

selector=#wrapper
property=display
value=block

Continue reading

After designing a layout for a web site, we obviously start converting it into HTML during this session as a web designer we mainly concentrate on cross browser compatibility but we also need to concentrate on some basic seo things like…

1. Using Correct Doctype.

2. Using Meta Content and Meta Keywords.

3. Using Alt tags for Images.

4. Using Valid HTML and CSS code.

5. Make your web site load fast.

Continue reading

When I surfing the internet I used to find the web is overflowing with sites that use horribly invalid, broken, and inaccessible markup. Even sites built by people who have been in the web business for many years, and who really should know better, are full of problems that shouldn’t be there. The reason? Ignorance, laziness, lack of time, bad tools, you name it. Yes, I’ve been guilty of making many mistakes myself through the years. However, I do my best to learn, and avoid making the same mistakes over and over again.

Here’s a list, in no particular order, of some of the most common mistakes that even experienced web professionals tend to make:

DOCTYPE confusion
Completely missing, incorrect, or in the wrong place. I have seen HTML 4.0 Transitional used in documents containing XHTML markup as well as in <frameset> documents, DOCTYPE declarations appearing after the opening <html> tag, and incomplete DOCTYPES.

Continue reading

CSS Hacking

A CSS hacking is basically about exploiting one browser bug to solve another. Now a new browser comes out that solves the exploited bugs, but not the other and people start advocating hacking to be stopped. It’s not that simple. Hacks are wrong (forget what I said in Implement CSS 2.1. The reason they are is that using them might prevent further enhancements to a specification. Something that’s invalid now might be a feature in the future.

Arriving at this point in my little rant I realize that the only point in not updating your site to exclude CSS hacks is that the intentention is probably wrong. Let me explain. Updating for Internet Explorer 7 should not be necessary, in theory it fixed its CSS bugs and besides that _height:1% is now ignored, it also supports your nice method of float clearing using generated content. Except that it doesn’t. And there is the real problem. The day a comment before the DOCTYPE no longer triggers quirks mode I certainly hope they fixed all those nasty little buggers.