8 Common CSS Mistakes and How to Fix Them

CSS has the distinction of being one of a handful of web technologies that newcomers tend to learn by doing. The reason for this is that CSS is not seen as something as large or as serious as a programming language like C# or Python, but rather as a tool to be used “just in time”, without paying attention to best practices. The result of this treatment is that quite a few web designers attain an incomplete knowledge of CSS and its problems, leading to broken layouts and hours of fruitless debugging. Here are the eight most common mistakes that web designers of all experience levels commit.

1. Not Reading the Specifications

The W3C CSS 2.1 spec is, at the moment, the only document to fully lay out all of the features of CSS in any detail. Most of it is dry, but thankfully it’s short with a lot of useful parts. Often when designers try to explain a particular feature of CSS to each other, they get a few things wrong. It’s a better idea to refer to the standard when something is unclear. Here are a few pages in the standard that are particularly useful: The standard is constantly changing and it’s important to keep up with it. With the coming browser support of CSS3, not knowing the formal basics of CSS2 will be a major disadvantage for web designers.

2. DIV soup

The gravest sin of the newbie CSS designer is DIV soup. This is what happens when there are way too many DIVs in the markup to achieve a certain (sometimes simple) effect. Recent table-to-CSS converts often use DIV tags as if they were table cells, when such use is unwarranted and pollutes the markup. DIV soup creates very real problems: pages load slower, DOM parsing is slower, more CSS needs to be written, and the code becomes less maintainable. With the advent of modern CMSs, DIV soup becomes inherent in the system, since a component that uses too many DIVs might be replicated quite a few times on the same page.

Motivation for DIV soup appears to come from a basic misunderstanding of how stylesheets cascade. For example, a designer might create 3 nested DIVs and apply a particular style for each DIV, say a background-color on the first, margin and padding on the second, and font-size on the third. What the designer doesn’t realize is that, unless this structure is absolutely necessary due to surrounding elements, all of these properties can be combined and used on only one DIV. Another reason for DIV soup appears to be the desire to use DIV tags in place of more appropriate tags like H1/H2/H3, or UL/OL and LI. This practice should also be avoided as it creates problems for people using screen readers, older browsers, or mobile browsers.

3. ID vs. Class

This is a common problem with CSS designers who haven’t quite mastered the logical side of CSS layouts. To clarify: IDs are for one item and classes are for many items. Think of it as a distinction between your identity and the city you live in.  An ID is “John Q. Smith,” but a class is “Metropolis, USA.” There are many other people who live in Metropolis, USA, and they are all subject to the same rules as you, such as taxes and other laws. But John Q. Smith is a unique individual and only a very small set of rules applies to him, such as his weight and his height. However, don’t make every collection of elements an excuse to slap a CLASS attribute on them. This, again, is related to understanding how stylesheets cascade. If you can wrap a collection of elements in a unique ID, you no longer need all the CLASS attributes inside. This saves bandwidth and development time.

4. Ignoring Shorthand

I still see pages that dutifully declare border widths the long way, with border-left-width, border-right-width, border-top-width, and border-bottom-width. Reading that list is hard work enough, but writing it and maintaining it is doubly inconvenient. CSS designers should learn immediately how to reduce the typing necessary to style elements. The most important pattern is that for widths. You’ll see this pattern repeated in other properties, so learning it is important. It goes as follows: top, right, bottom left. You can think of it as going clockwise starting from the top. What this pattern means is that when you specify units in shorthand, they’ll be applied to the top side first, followed by the right side, the bottom side, and finally the left side.

/*The above equates to the following:*/
border-width: 1px 1px 1px 1px;
You’ll note that in the above example, the width for all the borders is the same. There’s shorthand for this situation as well. Simply write border-width:1px to assign a 1 pixel border to all border sides. What if you have border widths that are the same on opposite sides, e.g. 1px on top and bottom and 2px on left and right? No problem, there’s a shorthand for that, too: border-width: 1px 2px, that is top/bottom first, then left/right. Finally, there’s shorthand for almost all declarations. Here’s a short list, more can be found here and here:
  • font: style, weight, size, family. Example: font: italic bold 12px Helvetica
  • border: width, style, color. Example: border:1px solid #ccc. Note: you won’t be able to set widths using the shorthand method described above here. You’ll have to declare the necessary widths separately.
  • background: color, image, repeat. Example: background: #000 url(image.png) no-repeat. Note: the image sits on top of the color, so if the image is transparent or if it doesn’t repeat, you’ll see the color under it. To avoid this, declare color to be transparent.
  • Colors written in hex can be condensed. Instead of #111111, write #111. Instead of #44ff77, type #4f7. Instead of #00ffff, type #0ff.

5. Ignoring Doctype

Web browsers were designed to handle almost any written mess one might call their web page. Tags closed in the wrong places, tags not closed at all, tags closed but never opened, the list goes on. It’s safe to say that if you’re not particularly up to speed on best practices in HTML and CSS, browsers will attempt to accommodate whatever markup you write. That’s not to say you should deliberately avoid learning best practices, since different browsers will render broken code differently, leading to many headaches later on. One best practice you should immediately adopt, however, is the declaration of a DOCTYPE. In the bad old days of HTML 4, you had to choose between a strict doctype, a transitional doctype, or something entirely different. Fortunately, browsers from IE6 and up understand the new HTML5 doctype. What the declaration of this doctype does is it throws the browser into standards mode, as opposed to quirks mode, which brings to light any and all lurking bugs in your CSS, instead of accommodating them.  The doctype is very easy to declare, just remember to put the following as the very first line of your HTML:
<!doctype html>
That’s it. This pithy line makes your HTML at once future-proof and past-proof. Make it a habit to always declare a doctype first.

6. Improper Use of Units

Font sizes shouldn’t be declared in pixels. We’re all guilty of this (yours truly included), mostly because of old habits from the tables era, where “pixel-perfect” meant “it looks good on 1024×768.” Though 1024x is still the most common resolution, wider widths and taller heights are becoming the norm across the world. This means that people are increasingly looking at smaller text on larger screens. I think most designers would agree that a huge part of web design is typography, but in modern times, function trumps form. Text can be, and should be, resizeable, since reading 10px Verdana on a 1920x screen is not only painful, it’s time-consuming. The solution to this problem? Declare your font sizes using the em unit, as in font-size:1.2em. This means that the font size of a particular element is 1.2 times the default font size, which is 16 pixels in Firefox and Internet Explorer. A very important benefit of this practice is that your entire site’s font size can be increased by simply changing the BODY tag’s (or any other container tag’s) font-size property. Doing this with pixel sizes is impossible, unless one uses the zoom function of the browser. Font sizes should also not be declared in points (pt), centimeters (cm), or any other unit best left for the print stylesheet. Avoid percents, since 1em is functionally equivalent to 100%, yet the latter takes up more room and has its own quirks.

7. Using Clearing Elements

Stop writing <div style=”clear:both”></div>. Furthermore, stop writing that convoluted mess element:after {content:”.”;clear:both;visibility:hidden;height:0;display:block}. These are hacks, not best practices. Start using overflow:hidden on container elements ASAP, since this is the simplest way of clearing floats. Here’s all the code you’ll ever need:
#container {overflow:hidden}
/*IE6 hack*/
#container {display:inline-block} #container {display:block}
That last part isn’t necessary in most cases. Sometimes, IE6 will annoyingly clip the containing element at some arbitrary position, at which point you’ll have to use the hack, but with IE6 being phased out, you will almost certainly never have to worry about this. For more information as to why overflow:hidden has this magic power, read the CSS standard page on block formatting contexts.

8. Ignoring Validators

Thankfully, this mistake has been disappearing from the web designer community as more and more people have become standards-conscious and are proud to state that their sites validate. Unfortunately, the rest of the web has yet to realize that invalid markup means more work later on. Here’s a prime selection: CNN.com has 65 errors, Amazon.com has 1228 errors, and that’s just HTML! The CSS validator catches 70 errors for CNN.com and 20 errors for Amazon.com. Though a few of these errors are excusable (non-standard CSS3 features like rounded corners), most of them are strange and out-of-place at large, corporate sites. Make sure you always validate your pages using both the HTML validator and the CSS validator.


Ivan M is a graphics pro. Find out more at his site: imsky.co.

Howdie stranger!
If you want to participate in our photoshop and photography contests, just:


46 Responses:

  1. Tony says:

    Thank you for the overflow:hidden tip – This should help with IE6 related migraines.

    ( 2 years and 1931 days ago )
  2. digitalvineyard says:

    Thanks. Useful tips. The new doctype is new to me and really good to know.

    ( 2 years and 1931 days ago )
  3. bradley says:

    Regarding #4, you can shorten it even further to either:

    border-width: 1px;

    Which achieves the same thing.

    ( 2 years and 1931 days ago )
  4. Craig Abbott says:

    Cracking post – Thanks for sharing

    ( 2 years and 1931 days ago )
  5. ESN says:

    CSS shorthands are very handy and it helps save a few bytes from your css file. For some strange reason, I can never remember the shorthand for font by heart.

    ( 2 years and 1931 days ago )
  6. Hian Battiston says:

    Thanks for the tips!

    ( 2 years and 1931 days ago )
  7. Rachel says:

    Good to know it’s not just beginners like me muddling along.

    I’ve recently converted my website from an office live wysiwyg to code I can edit so I’m doing a lot of code shortening and CSS conversion for the text. Can’t believe that more people don’t use smaller code if they can they should.

    I really liked you description of ID v class it was the easiest to understand out of everything I’v read so far.

    I’m a long way from understanding layout code though, so my tables will stay for a while.

    ( 2 years and 1930 days ago )
  8. Kai Chan Vong says:

    Your concept of .bluethings being overly used was spot on. However your usage is flawed… an ID is for use around naming things, not classification.

    For this reason it should be like so:
    .bluethings LI,LI.bluethings { color:blue; }

    That way you’re saving the ID for the important stuff which is specific.

    I’m going to be documenting some more of my examples and concepts on how to use CSS better too :) But good job on sharing some of your thoughts.

    ( 2 years and 1930 days ago )
  9. Tanner says:

    The fact that there are developers who use SO many nested divs is truly sad. If you can’t create a great layout using only a few divs, you might as well go back to using tables in your design (which is so 1990).

    ( 2 years and 1930 days ago )
  10. Tony Gray says:

    All good tips! I recently learned about the overflow:hidden tip and you would not believe (or you might) how many problems that solves in all my pages. Good post!

    ( 2 years and 1930 days ago )
  11. David | WebModia says:

    Just a few nudges here. You are writing this for CSS newbies, attempting to help them avoid common pitfalls that make getting started with CSS difficult. As I’ve said before on similar posts (even on another of your recent posts), this is great information to share but please be sure you are promoting best practice… here are some considerations for improving your suggestions:

    3. ID vs. Class – I just think your example should be altered b/c as it is, it implies usage of presentational class and ID names. You use “#bluethings” and “.orange” for example – but what if down the road a redesign calls for those “#bluethings” to actually become green, and the “.orange” elements become red? This is the problem with presentational naming conventions.

    Instead, best practice is to use structural, semantic naming conventions. So if the “#bluethings” element is a grouping of related items, a better ID name would be a semantic name that describes that grouping’s purpose or function – i.e. if it is a group of articles, give it an ID of “#articles”. Bottom line: keep structure and presentation separate.

    7. Using Clearing Elements – I also prefer the “overflow:hidden” method over the “element:after” solution (originally popularized as the “clearfix” method by the folks over at Position Is Everything dot net). But be sure to give that container a width as well if possible… otherwise, you do occasionally get some undesirable behavior and not just in IE6.

    I wouldn’t go so far as to call the PIE clearfix method a hack. It certainly has it’s purpose, for example you may find that you have groups of floated items used repeatedly throughout your site – a quick and perfectly semantic solution here is give these containers that group together floated elements a class of “group” and then use the clearfix method on that class name (i.e. “.group:after {…clearfix rules here…}”). (Dan Cederholm dedicated an entire chapter to this rather simple concept in his latest book…). This solution works when you cannot declare a width, for example, as you would need to do with “overflow:hidden” if you want to keep it working across browsers.

    Ultimately, it doesn’t pay to swear off any solution, just so long as you understand the reasons for why one solution is a better fit in a particular situation.

    ( 2 years and 1930 days ago )
  12. ben says:


    That makes no sense at all. Looking at your “portfolio” you’ve never gone any wear near creating a layout as complex as the likes of Amazon, for example. The work you create will be very easy to knock up in a few divs, as there’s nothing much too it.

    Cant stand all the pretentious dev’s that moan about “div soup” or whatever you want to call it. It doesn’t matter, for a start. Look at the examples cited above, I’m sure any of you would swap your 5 div mark-up for the traffic and conversion rates seen on Amazon or ebay.

    People like you, @tanner, who create sites like yours, which have no real “design” or layout to them, can do so in a few divs have no concept or understanding of working on such large scale projects, and as such jump on the snobby pretentious “Elliot jay stocks*” said so bandwagon.

    *Elliot was just an example of the sort of person who’s “opinion must be rule” in the web design community that really pisses me off, I don’t know if he has spoken about the overuse of div’s or not, but its the sort of unimportant thing he would spend time discussing.

    ( 2 years and 1930 days ago )
  13. Web Design Maidstone says:

    Awesome post, really clearly written and enlightened me on a few points!

    ( 2 years and 1930 days ago )
  14. craig says:


    As someone who maintains a front end for a deep highly functional site with a team of programmers, I can tell you that div soup is actually a problem that can slow down development and increase the possibilities for regression.

    Using semantic markup when possible is highly important for maintaining a layout and very useful when passing around the code. While I don’t bend over backwards to remove divs, I am always looking for ways to get the same task done with less markup.


    You comment post reply box exceeds the width of its container in Firefox on a PC.

    ( 2 years and 1930 days ago )
  15. Jenna Molby says:

    Great article! I’m guilty of the div soup one :P

    ( 2 years and 1930 days ago )
  16. Amber Weinberg says:

    Great tips, I’ve seen a lot of beginning developers make these mistakes :)

    ( 2 years and 1930 days ago )
  17. Jon R. Humphrey says:

    Thanks for reminding me of the Overflow:hidden trick, I totally forgot that!
    *Jon trundles off to clear his .clears!*

    ( 2 years and 1930 days ago )
  18. imsky says:

    Thanks everyone for your kind words :)


    Kai, there are many ways one can use the “anonymous elements within a named container” construct. You can use classes, you can use LIs in a list, however LI.bluethings is exactly what I tried to advise against. Having 20 elements in a row with the same class attribute is not a good practice.

    David, the names are examples only, I don’t even touch on semantic markup in this post. Setting a width on a container when using overflow to clear is, however, a good piece of info.

    Ben, the conversion rate of Amazon has nothing to do with its overly complicated layout. They could shave off hundreds of thousands of dollars in yearly bandwidth costs if they reduced the complexity of their markup, all the while keeping their design the same.

    Craig, I don’t control the site elements here, sorry.

    ( 2 years and 1930 days ago )
  19. Best Content Management System says:

    Some of the errors found on the W3C site are at times small problems that could be ignored. Definitely make sure there are no red flag errors or else your pages will never be indexed properly into the search engines.

    ( 2 years and 1930 days ago )
  20. jeremy says:

    Excellent article. You really shed some light on IDs vs Classes and on how to use Em units properly. This was extremely useful, thank you.

    ( 2 years and 1930 days ago )
  21. Anon says:

    Sorry, but W3C validition is a croc. You try any site in there and it will usually spit out some errors, even this site had 24 errors….

    That’s why I always say test, test, test. Some developers brag that there site is validated but when you test it across the browsers and across the platforms it doesn’t work!!! ha ha.

    I would rather have a site that works correctly across platforms and browsers yet spits out a couple of WC3 errors, than one that is W3C validated and doesn’t work across browsers….

    ( 2 years and 1930 days ago )
  22. Scarlett says:

    Thanks for a great read…comments as well. I agree that although the topic is not semantics per se, the stylistic naming example could be structural instead for greater clarity re: the issue of markup vs. style. Thanks again for the info on overflow:hidden.

    ( 2 years and 1930 days ago )
  23. ben says:

    @imsky No, they really couldn’t, it doesn’t make that much of a difference. My point is that despite there “poor markup” these sites fill there purpose, so who are we to call out the developers? In most other industries, the big brands set the standards for the rest, in webdesign, the pretentious developers shout about what the big brands are doing “wrong”, and the big brands ignore it as they know it makes little to no difference. The fact is the cost of re-developing a site like amazon far outweighs the savings on bandwidth, which your probably getting confused with data transfer anyway.

    @craig I agree with semantics, in principle. I agree with standards, but I’m realistic. I work in a corporate environment were (excuse the cliché) time is money, my boss isn’t a designer or developer, hes a business man, and saying “its going to take an extra couple of hours because i need to fix this div soup” just isn’t a viable option.

    The fact of the matter is the differences in page load time are tiny. No-one would notice the difference, and it really doesn’t save much data transfer wise. If it did, and you honestly believe Amazon could save hundreds of thousands of dollars a year by reducing the amount of divs in there site structure then you are a fool, and have no place in writing blog posts that attempt to speak with some knowledge or authority. If this was the case, they would of done it. Its not like they cant, don’t have the funds, or the business expertise to spot the situation in the first place.

    What makes you think a small time unknown blogger like yourself has thought of a solution that could save Amazon millions of dollars over a couple of years, that they hadn’t already considered?

    ( 2 years and 1930 days ago )
  24. tim kretschmer says:

    using overflow:hidden is only practiceable if you have fix weight and height

    if the containers are flexibel you must user a clear.

    ( 2 years and 1930 days ago )
  25. Maikelhaas says:

    is ” really enough? I’ve always copy pasted whole lines like ”

    Also I guess I have to watch the .class and #id more in the future.

    Thanks for writing!

    ( 2 years and 1929 days ago )
  26. Maikelhaas says:

    In the previous commented I referred to the Doctype quotes, I did not know code was not allowed.

    ( 2 years and 1929 days ago )
  27. Victor says:

    Hi, just a minor correction: in 4.”Ignoring Shorthand” you refer to the pattern of width values as counter-clockwise when it’s actually “clockwise”.

    Keep on posting ;)

    Victor from Portugal

    ( 2 years and 1929 days ago )
  28. deborah says:

    This is the best “CSS Mistakes” list *ever* – I think you hit every single one of my pet peeves. I’ve rejected CSS for some of these items (or made an intern go back and do it again).

    ( 2 years and 1929 days ago )
  29. Bob says:

    So in sample #7 you suggest to stop using a “hack” and do something else, which actually may require another hack to get to work. Seems like rubish to me.

    ( 2 years and 1929 days ago )
  30. imsky says:

    Ben, your argument would be valid except that big names redesign once every 2 years or so. Just go look at the 2006 and 2008 Amazon pages. This supposedly “apathetic to design” company changed such little details as the design of the “Cart” and “Your Lists” buttons. More examples here: http://www.pxleyes.com/blog/wp-content/uploads/2010/03/amazon.jpg Facebook has a Lite version that was specifically designed to save bandwidth, so it looks like the “big brands” know it makes a difference.

    Maikelhaas, yes it is enough. As always, check your site in older browsers if this is a concern for you.

    Victor, you’re right, I corrected it.

    Bob, the hack I refer to doesn’t involve useless markup or CSS features not supported by older browsers. IE6 as of today has around 7%-10% market share. Not only does the IE6 “hack” have very specific applications, it won’t be necessary a year from now.

    ( 2 years and 1929 days ago )
  31. Adam Hermsdorfer says:

    I’m guilty of the div class=”clear” and I will try use the overflow:hidden in the future. Thank you for bringing up the point about some CMS’s, particularly eCommerce, who use Divs as if they are tables. I really look forward to HTML5/CSS3 and having the markup be even more cleaner.

    ( 2 years and 1926 days ago )
  32. Lorie says:

    1st visit to this site. I learned some excellent tips, 8 of them, actually 9, the first 8 we’re excellent, the 9th one, sad. Why sad? Sad because it seems there are some, and I mean ‘SOME’ people who post blogs just to put someone else’s intelligent ideas that we’re written with good intent, took the time out to help to others (for free), and some people envy their knowledge rather then be greatful.
    I only write in regards to 1 blogger in particular, everyone knows who you are. My advice is: If you don’t have anything positive, or nice to say, don’t say anything at all. Look in the mirror at your many flaws, only people with so many flaws would be so mean. Use constructive feedback, not putdowns and be considerate of others, and just be greatful. No ones interested in reading your trashing of other bloggers.

    Thanks for the 1st 8 tips!

    I probably won’t visit this site again, if I do, I’ll skip other peoples feedback.

    Peace Out!

    ( 2 years and 1926 days ago )
  33. Regis says:

    Nice basic article… except #7 regarding clearing.

    Why in the world would you recommend an element that uses “clear:both;” (or a dynamically created element ala the :after pseudo-element) as bad practice to clear an element? Furthermore, how can “clear:both;” be a hack for clearing? It’s in the attribute name! Sorry, but “overflow:hidden;” is more of a hack.

    The overflow hidden method is a neat little “happy accident.” I’m not saying it should be avoided, but you do have to be careful. Overflow hidden will, as you know, hide all the content outside of the box. This means everything from positioned items, box-shadows, outlines, etc.

    It comes down to using ‘overflow:hidden’ when you want content that may fall outside of a box to be clipped and using ‘clear’ you want to clear an element. That way, when you later decide you want to position an element outside of your box, or you want to start using some CSS3 effects (like box-shadow), etc. you aren’t screwed because everything is overflow:hidden.

    ( 2 years and 1925 days ago )
  34. Vinicius Almeida says:

    Awesome article!

    Very helpfull!


    ( 2 years and 1924 days ago )
  35. Tim says:


    Adding an extra div to your markup simply for clearing is a hack, and bad practice.

    But I somewhat agree with some of your comment… Overflow:hidden isn’t the most elegant solution. The :after method is far more useful, and can be accomplished without adding extra classes to your markup.

    #6 is also up for debate again. I would have agreed with you a year ago, and I’m on the fence currently. With the increased popularity of page zoom in browsers there are plenty of people out there encouraging the opposite: go back to using px.

    ( 2 years and 1923 days ago )
  36. Paul Fleischanderl says:

    nice article! realy!

    BUT: #6 was not in mind when you create this theme?

    ( 2 years and 1922 days ago )
  37. Allen says:

    “browsers from IE6 and up understand the new HTML5 doctype.” Are you sure about that? IE 6 was finished before HTML5 was dreamed up.

    ( 2 years and 1920 days ago )
  38. Dan Hensby says:

    A nice article all round; however, I can’t say I agree with #6. Before I go further, I’ll say that I don’t think there is a ‘right’ or a ‘wrong’ way; people should choose what they like and keep consistent.

    You justify em being better than px because 1em = 16px by default in FF. Thus, 1.5em = 24px, etc. So really, you are still addressing pixels, it’s the same as saying 16px or 24px, just not by name. The key difference I see is that ems are relative and pixels are absolute – so, if someone changes their default font size, then everything will scale. But, all modern browsers have zoom features that make ems unnecessary. In fact, the only thing I think IE6 gets ‘right’ is that when you use zoom, px don’t scale and ems do! (px are absolute, so should always be the defined size)

    I use px to do all the measurements because it saves time with calculation. Not only do we not need to work out how many em for a 13px font size. Plus because it is relative to the element you are nested in, it gets even harder to manage and more complex. It’s essentially a maintenance nightmare because you can’t instantly look at the CSS file and see the font size and make sure it is correct according to the design.

    eg: If we declare this rule ul,li,li a { font-size: 1.2em; } where 1em = 10px is the base in the ul, then the text in the anchor will be ~17px. but if we decide then wrap the UL in another div with the font size decoration of 1.2em, then the font size of a the anchor tag will be increased to ~21px which would be unintentional and a pain to debug.

    ( 2 years and 1919 days ago )
  39. Andy says:

    Nice post, an interesting and educational read!

    @David – I agree with your point of capturing a semantic meaning with the value of an id, rather than coupling it with presentation detail. I suppose in the post, a better id might have been “oddOneOut”, which captures the meaning that element conveys in the example.

    A minor quibble that had me confused (an admittedly easy task :-P ) for a sec:

    “4: Ignoring shorthand … It goes as follows: top, right, bottom left. You can think of it as going counter-clockwise starting from the top…”

    That ordering is clockwise rather than counter-clockwise no?

    ( 2 years and 1918 days ago )
  40. Kim_Office_Team says:

    @Rachel — I’m sure the community would really value hearing about your thoughts on converting from the Office Live WSYWIG to CSS. You can join the conversation at the Office Live page on Facebook, here: http://www.facebook.com/officelive.

    Microsoft Office Live Outreach

    ( 2 years and 1917 days ago )
  41. Rick says:

    I totally agree with @Dan Hensby there is no right or wrong for font-size. I prefer to use pixels now as well since nested items will not inherit the parents size.

    Also we need to remember it was recommended to use ems back when most browsers would not allow user to zoom text that was in pixels. Nowadays modern browser zoom entire pages.

    Good article, thank you

    ( 2 years and 1866 days ago )
  42. Diseño Web Toledo says:

    Thx for sharing the tips.

    css is simplicity

    ( 2 years and 1828 days ago )
  43. Brett Widmann says:

    Very simple mistakes that can ruin the whole coding project! Thanks for putting together a list with some solutions.

    ( 2 years and 1698 days ago )
  44. Ragesh says:

    So nice… thank you very much…!

    ( 2 years and 1637 days ago )
  45. Emerson says:

    I genuinely appreciate blogs like these that not only provides data just to sell their item but also gives info that is practically helpful to the people who are concerned.

    ( 2 years and 1573 days ago )
  46. Andrew says:

    CSS shorthands are very handy and it helps save a few bytes from your css file.

    ( 2 years and 904 days ago )

Leave a Comment