Do not use #id selectors, because they are not reusable. Good enough reason.
However, there is a nice debate here.
. css IDs are like singletons (can have only one instance), hence not re-usable.
. IDs refers specific element. Abstracting is difficult.
Points against the statement:
. using IDs are fast. (poor point. the speed gain is low and negligible)
Read the comments for more fun. | Don’t use ID selectors in CSS | Screwlewse | Don’t use ID selectors in CSS | Screwlewse | Don’t use ID selectors in CSS Posted on: July 28, 2010 / Categories: UncategorizedLately I have been testing out performance among css styles and I found that some of my very smartfriends, started asking,”why aren’t you testing using IDs for the unique sections of the page?”.This wasn’t a hard answe...
User login
Who's online
There are currently 0 users online.
Popular content
-
. good thought on Node Block. . don't pr...
11th Jan, 2013 -
Post-mortem of a Deployment Issue.Step by step digging into it Part I
17th Aug, 2013 -
Web integration tests in F# backed by se...25th Mar, 2014
-
CiViCRM profile update page in Drupal using CiViCRM API3rd Jul, 2013
-
Popular Domain Driven Design Overview
23rd Jan, 2012
tarek.jubaer
Fri, 2014-03-07 08:46
Permalink
It should not be a hard rule to use/not use any selectors. It totally depends on the pattern developer is comfortable with. But must be optimized and easy to maintain.
ron
Fri, 2014-03-07 09:01
Permalink
agree. not a hard rule..
While writing css, we will be beneficial if we practice the basic patterns we follow in code like
. not repeat code
. where necessary override css using inheritance
using id selector prevents re-using of code, so we shall avoid this when we have other options .. e.g.: adding two classes
Add new comment