Replacing outdated tag attributes

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

I am evaluating EWD, which seems to be an improvement over FrontPage.
In code view, the program alerts you to items that are not HTML 4.0
compliant.  For example, in this line...

<td align="center" valign="middle" width="173" height="100"
bgcolor="#ffffff" class="bdDkBluBld" colspan="3">

I am told that the following are "outdated and newer constructs are

My questions are, WHAT are the newer constructs and WHERE do I find
information on what to replace them with?

- Bob

Re: Replacing outdated tag attributes

silverbob wrote:

Quoted text here. Click to load it

I expect it means CSS (cascading stylesheets).

You could (for instance) write <td style="width: 173px; height: 100px;
background-color: #ffffff"> , though applying styles on a per-element
basis wouldn't really give you the major benefits of CSS, like being
able to apply the same stylesheet to multiple documents.


Re: Replacing outdated tag attributes

silverbob wrote:

Quoted text here. Click to load it

Further, see this: /
and then work through the tutorial. It's a fairly good one.

   -Warning: I brake for lawn deer

Re: Replacing outdated tag attributes

silverbob schreef:
Quoted text here. Click to load it

The reason why these things are outdate is that they define the way
your page looks and not the contents of your page. They idea now a days
is that you split up the content of your page (your markup in html) and
the way your page looks (the style, defined using css = cascading
stylesheets). So idealy, there is nothing in your html page that
defines your style, that would be all in your css file(s). The big
advantage is that when you want to change the way your page looks, you
have to rewrite the css and you don't have to change anything to the
html. But going this far requires you to really know css very well and
that takes up some time and experience. For example, you then can't use
a <table> tag any more for splitting your page up in a header, footer,
menu and so on. You have to define all these parts in different <div>
tags and define in css where the div blocks have to be placed and how
they have to look.

But this is all in theory. In reality, you have to try to do this as
good as possible, but sometimes it is just a lot easier to leave
certain style defining stuff in the html, for example the <table> tag
for creating a header, footer, menu, ...

I nice example of a page that demonstrates the theory of complete split
up of markup and style is CSS Zen Garden. That is one page where
different people can post their css for. You can change the style of
the page to a style that someone created, then the css changes, but the
html stays the same. It is amasing how much you can make one page look
completely differently using just css. Take a look around: /

But don't expect if you start out with css, to be able to do such
amazing stuff right away. As I said, it takes some time to get to know
it. A really good help would be to use Dreamweaver instead of Frontpage
to create your pages and css. It has excellent support for css!


Re: Replacing outdated tag attributes

Quoted text here. Click to load it

So do you mean that it says that align, valign etc. attributes in <td> are
such items? And that it really talks about HTML 4.0 and not HTML 4.01?

Furthermore, that it declares them as outdated (which is a reasonable
position), yet gives no hint of what you should do with them?

Get your money back.

Jukka K. Korpela ("Yucca")

Re: Replacing outdated tag attributes

The actual message is "The World Wide Consortium now regards the
attribute, <> as outdated. Newer constructs are recommended."  This is
a beta release, so I haven't put out any money.  I've submitted a wish
to expand on that message.


Jukka K. Korpela wrote:
Quoted text here. Click to load it

Re: Replacing outdated tag attributes

silverbob wrote:
Quoted text here. Click to load it

HTML is the work of the World Wide Web Consortium, or W3C
W_2_C are _much_ scarier, and will be the topic of the next Dan Brown
book. TINC.

OTOH, the CSS 2.1 recommendation is much more readable than Dan Brown.

Site Timeline