11330

Is using the style attribute frowned upon?

As someone who is beginning to make a transition from table based design to full CSS I'm wondering if using the style attribute to make adjustments to elements is considered "cheating" and if absolutely ALL presentation should be strictly in the style sheet?

See also:

A question of style - approaches to styling and stylesheets

Answer1:

There are cases where you know for sure that all you want to do is tweak the style of this one specific element, and nothing else.

In those cases you can happily use an inline style attribute. <strong>But then</strong>, at some point in the future, you'll realise that in fact you need to apply the same style to something else, and you'll realise you were wrong.

Been there, done that. 8-)

Answer2:

I feel there's an aspect that has not been touched upon here: the distinction between hand-edited HTML snippets and generated HTML snippets.

For human editing, it's probably better and easier to maintain to have the styles in a file.

<strong>However</strong>

As soon as you start generating HTML elements, with server-side scripts or with some kind of JavaScript, be sure to make all styles required for basic functionality inline!

For example, you wrote some kind of JavaScript library that generates tooltips. Now, you will inject DIVs into your page, that will need some styles. For example, position: absolute and, initially, display:none. You may be tempted to give these elements the class .popup and require that this class has the correct definitions in some CSS file. After all, styles should be specified in the CSS file, right?

You will make your JavaScript library very annoying to reuse, because you can no longer simply copy and invoke one .js file and be done with it. Instead, you will have to copy the .js file, but also have to make sure that all styles required by the script are defined in your CSS file, and you have to go hunting for those, and make sure their names don't conflict with classes you already have.

For maximum ease of use, just go ahead and set the required styles directly on the element as you create it. For styles that are purely for aesthetical purposes, such as background-color, font-size and such, you can still attach a class, to give the consumer of your script an easy way to change the appearance of your script elements, but don't require it!

Answer3:

You can use the style attribute, but the point of using CSS is that you make a change in a single file, and it affects the entire site. Try to avoid it as much as possible (old habits die hard)

Answer4:

It's not maintainable. All of us have done it. What you're best to do is put every adjustment into a style. Let me teach you something most developers do not know about CSS ... you can use N styles at a time.

For example, imagine you have a great style for colorized divs called someDIVStyle:

.someDIVStlye { background-color: yellow; ... }

You want to use it, but just want to adjust the background-color to blue. Many people would copy/paste it and then make a new style with the change. However, simple create a style like this:

.blueBackground { background-color: blue; }

Apply it as such:

<div class="someDIVStyle blueBackground">...

The style furthest to the right always overrides the properties of the styles preceding it. You can use a number of styles at once to meet your needs.

Answer5:

I agree with some other posters that it is best to keep the style information in the stylesheet. CSS tends to get complicated quickly, and it is nice to have that information in one place (rather than having to jump back and forth from HTML to stylesheet to see what styles are being used).

A little off-topic tip: Pressing F12 in IE8 brings up a great tool that lets you inspect the styles of elements in web pages you're browsing. In Firefox, FireBug does the same thing. Those kinds of tools are lifesavers if you want to know how a style change will affect an element.

Answer6:

It's a very "personal" question, to me the word "ALL" is a very strong word. You should do your best to have most of the styling in your css. but you can use style occetionally if it makes your life easier.

Answer7:

Generally it is best to have styles on the style sheet especially if it will be used multiple times, but using the style attribute is definitely not "cheating". A quick look through the stackoverflow source shows many examples of this.

Answer8:

Yes, it's kind of cheating, but it's up to you if you want to cheat a little. :)

The fundamental idea of having the styles in a style sheet is to separate the content from the layout. If you use the style attribute you are still mixing layout within the content.

However It's not that terrible, as you can quite easily move the style into a class. It's quite handy during development to be able to set a style on a specific element so easily without having to make up a class name and worry how the style will cascade.

I sometimes let the style attribute go through in the production code, if it's something that is specific for just one page, and if it's doubtful that it will be there for long. Occationally just because I am pressed for time, and it can be cleaned up later on...

So, even if you use a style attribute sometimes, you should still have the ambition that all the styles should be in a style sheet. In the long run it makes the code easier to maintain.

Answer9:

As others have said, in general, no.

However, there are cases where it makes perfect sense. For example, today I had to load an random background image into a div, from a directory with an unknown # of files. Basically, the client can drop files into that folder and they'll show up in the random background image rotation.

To me, this was a clear reason to dynamically build up the style tag on the div.

In addition, if you're using, for example, the .net framework with webforms and built-in controls then you'll see inline styles used anyway!

Answer10:

There can be very good reasons to put style information in a specific page.

For example, if you want to have a different header background on every page (travel agencies...), it is far easier to put that style information in that specific element (better, in the head of the document...) than to give that element a different class on every page and define all those classes in an external style-sheet.

Answer11:

The style attribute does have one important use: setting style programmatically. While the DOM includes methods to manipulate style sheets, support for them is still spotty and they're a bit heavyweight for many tasks, such as hiding and showing elements.

Answer12:

Yes, the style attribute is frowned upon in general. Since you're moving to the CSS method from table-based, I'd strongly recommend that you avoid inline styles. As a previous poster pointed out: bad habits are hard to break and getting into the habit of using inline styles for their temporary convenience is a mistake. You might as well go back to using the font tag. There's really no difference.

Having said that, there are occasions where it makes sense to use a simple inline style, but first develop the habit of using stylesheets. Only when you're comfortable with putting everything in a stylesheet should you start looking at shortcuts.

I think that's the general consensus of everyone who posted an answer

Recommend

  • .net dictionary with default value
  • How can I properly implement the nodejs Stream API?
  • Highlighting current page item in the nav menu with jQuery
  • Why would one use Dreamweaver Templates over PHP or Javascript for templating?
  • REST Web Service - Dynamic Query Parameters
  • how to set environment variables on google appengine?
  • WooCommerce REST Client API - Programmatically get consumer key and secret
  • SCons: modify intermediate builder calls
  • Javascript Unit test
  • Is there an easy way to “append()” two dictionaries together in Python?
  • CSS - Cursor Transition
  • Task processing status with a message queue
  • My Produce Consumer Hangs
  • Functions returning a const value [duplicate]
  • Ruby on Rails two create actions to two different controllers simultaneously
  • ILMerge: Rename internalized assemblies' namespaces?
  • dynamic server time
  • Adding millions of nodes to neo4j spatial layer using cypher and apoc
  • In powershell, using the export-csv cmdlet, my ints are being encapsulated by quotes any idea why?
  • Getting proper map boundaries
  • why 0.1+0.2-0.3= 5.5511151231258E-17 in php [duplicate]
  • Show records ordered with maximum price first in PHP & MySQL
  • android-support-v7-appcompat has same attrs as actionbarsherlock library
  • How to create two column output from a single column
  • Scanner nextInt() and hasNextInt() problems
  • ThreadStatic in asynchronous ASP.NET Web API
  • Why use database factory in asp.net mvc?
  • Can someone please explain to me in the most layman terms how to use EventArgs?
  • Window Size for Mac application
  • Statically linking a C++ library to a C# process using CLI or any other way
  • Comma separated Values
  • WPF Applying a trigger on binding failure
  • python regex in pyparsing
  • Error creating VM instance in Google Compute Engine
  • How to set the response of a form post action to a iframe source?
  • Hits per day in Google Big Query
  • how does django model after text[] in postgresql [duplicate]
  • Change div Background jquery
  • Qt: Run a script BEFORE make
  • reshape alternating columns in less time and using less memory