WWAAT

[sUn]

I didn't want to hijack Jpec's thread, so I'm just going to post this one.

If anybody good help me solve my Validating issue it would rock. 👍

Anyhow it's a .zip file, and it shouldn't take long to download. I don't have a good host at the moment.

Thanks.

Yes, it's minimalistic, there's only one page in the .zip file.

EDIT: I've taken this down, until I'm done.

 

[Shannon]

All img tags need an an alt attribute.

 

[sUn]

What do you mean?

<img src="images/splash3.jpg" width="636" height="130" alt="Splaash." />

That's the only part of my page that has an image. Where would I add the alt tag?

 

[Shannon]

Validate it and post up the errors.

Edit: I thought all those <a> tags were img's.

 

[Solid Fro]

You don't have a closing </div> tag before the closing </body> tag.

 

[sUn]

Hold on.

EDIT: Here.

 

[Shannon]

<h4 align="left">Homepage.</h4>

align = no no in XHTML 1.1/1.0 Strict. That's what CSS is for, although there isn't any need to left align anything.

As for the other one, yeah, you are missing the closing </div> tag.

 

[Matrixhasu77]

W3.Org's HTML Validator

Validate Away using that. I'm lazy, yes, but that's what I used to fix errors on my website.

 

[Sage]

Pretty good. 👍

I must say though that the semantics aren't good, especially those <br /> tags, the totally unnecessary <span> tags, and the fact that headers are marked up as parts of paragraphs. Personally, this is how I would mark up the "content" division:

<div id="content">

<h2>April 19, 2004.</h2>

<p>I'm still as lazy as I was about a month ago,
I'm still at the same stage on this website. The
Vancouver Canucks face the Calgary Flames
tonight Game 7. This'l be a very close game. But
I've once again started work on this website, and
I'm hoping to get it finished this time and not
postpone it. Damn site still isn't a validate site, I'll
work on that. Only section left to do is the Gallery.
Which takes forever.</p>

<h2>April 03, 2004.</h2>

<p>I lost the fully finished version of this website,
but I found the un-finished version. So I'll just re
work it, with maybe some better additions then
the now lost version.</p>

</div>

Also, change...

<h4 align="left">Homepage.</h4>

... to this:

<h1>Homepage</h1>

Then use CSS to style it, as well as re-styling the <h2> and <p> elements above.

 

[sUn]

Agh, sadly the canucks just loss.

Anyways, I'm going to edit it up; and notify you guys on how it is.


EDIT:

I'm still having a problem with the closing of the </div> before the </body> tag. When I do that, the whole website screws up, and I end up with 10-15 errors.

 

[Shannon]

Originally posted by Matrixhasu77
W3.Org's HTML Validator

Validate Away using that. I'm lazy, yes, but that's what I used to fix errors on my website.

I wish the W3C would provide a downloadable validator application. I hate having to go to their page all the time.

Originally posted by Sage
I must say though that the semantics aren't good, especially those <br /> tags, the totally unnecessary <span> tags, and the fact that headers are marked up as parts of paragraphs.

What is it with you and hating linebreaks? Sure, when people use them to place an image 10 lines down the page, they suck. But for something practical like so:

Lorem Ipsum
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Cras quis diam eu ante mattis dictum. Donec vestibulum nunc et dui. Etiam placerat nulla sed nisl. Sed vestibulum nibh et lectus. Phasellus vehicula wisi. Integer lorem ligula, venenatis sit amet, vestibulum et, suscipit ut, diam. Pellentesque ut ante vitae arcu cursus placerat. Donec vestibulum, augue non placerat aliquet, augue pede scelerisque urna, quis porttitor magna eros vel ipsum. Curabitur a neque eu sem sodales gravida. In hac habitasse platea dictumst. Sed turpis. Aliquam ut magna. Quisque scelerisque turpis non turpis. Vestibulum rutrum.

Naturally you'd use a <br /> to seperate the title from the rest of the paragraph there, and you don't get 20px or so of whitespace between as you would by adding a <h1>.

 

[Matrixhasu77]

Originally posted by Shannon
I wish the W3C would provide a downloadable validator application. I hate having to go to their page all the time.

Same here. It's rather annoying to have to jump online just to check errors. Of course, I edit my pages and upload them to my host anyway so it doesn't bother me that much.

 

[Sage]

Originally posted by Shannon
I wish the W3C would provide a downloadable validator application. I hate having to go to their page all the time.

Actually, I read on the Webstandards.org website a couple weeks ago that the W3C released a stand-alone validator, but to be honest, I haven't looked into it (I'll be perfectly frank in that I almost never validate my pages, because I already know most of the XHTML "strict" specs by heart (and I always encode ampersands), so I rarely need it).

What is it with you and hating linebreaks? Sure, when people use them to place an image 10 lines down the page, they suck. But for something practical like so:

Lorem Ipsum
Lorem ipsum dolor sit amet, <snip!>

Naturally you'd use a <br /> to seperate the title from the rest of the paragraph there, and you don't get 20px or so of whitespace between as you would by adding a <h1>. [/B]

I totally understand what you're saying, but it is an issue of semantics &ndash; for a pinch-assed tightwad like me (), a heading must be marked up as a heading, and a paragraph must be marked up as a paragraph. I should note that the W3C themselves have noted this, and thus are removing <br /> from the XHTML 2.0 specs.

I've almost never had a situation where I've needed the header to hug the paragraph, but in that case, some negative margins will works just fine.

I just stated that the semantics were off (and that's factual, not an opinion), and suggested how to make it semantic &ndash; Sunny doesn't have to do it that way if he doesn't want to, by any means. Just trying to tell people now, because several years down the road semantics will be a huge part of web design, because of the fact that more user agents (apart from desktop browser) will be grabbing pages. Trust me, that will become a key word in web development, though not yet.

 

[GilesGuthrie]

Originally posted by Sage
I should note that the W3C themselves have noted this, and thus are removing <br /> from the XHTML 2.0 specs.

That's a complete nightmare!

For those of us who are storing text in database fields, then echoing it to the browser, it's a disaster! PHP has a lovely function nl2br(), which takes a text string, and every time it detects a carriage return, it replaces it with <br />.

I hope W3C plan to have an alternative to that.

 

[sUn]

Originally posted by sUn
Agh, sadly the canucks just loss.

Anyways, I'm going to edit it up; and notify you guys on how it is.


EDIT:

I'm still having a problem with the closing of the </div> before the </body> tag. When I do that, the whole website screws up, and I end up with 10-15 errors.

I'm still stuck with that problem. I've gotten rid of the other problem.

 

[donbenni]

I like it a lot. Minimalism and that box layout rock Keep at it.

 

[sUn]

Thanks, donbenni.

 

[donbenni]

Worked a little on a layout, i think it's quite nice. Need to edit bluerobot.com's css still as it looks very similar to the original and yes it's very similarly shaped box wise to sUn's.

However would very much so appreciate:

- Code help (i'm not too fussed about this though, so long as it works)
- New colour scheme (blue's great, but it looks too bluerobot)
- Help with 'Introduction' blurb (i know nothing)
- General C & C

www.angelfire.com/pro/chopper/website.zip

 

[Matrixhasu77]

Originally posted by sUn
I'm still stuck with that problem. I've gotten rid of the other problem.

You needed an extra div tag before your closing body tag. I fixed that along with your align="left" error. In the CSS, I added text-align: left; under the h4 selector. However, that will align any text with the designator h4 to the left(I wasn't sure if thats what you wanted. If not get rid of it.).

Your page should be valid now... You had extra <.br> tags that I didnt think were neccessary, IMO. They added a scroll bar in Firefox.

 

[Sage]

*bumpity bump*

Regarding what I said about semantics, I just realized that there's a really easy way to close the gap between a header and a paragraph, without closing the margin on every paragraph... adjacent selectors.

Adjacent selectors simply mean an element that's adjacent to another. For example, in the following,

<h1>Heading</h1>
<p>First paragraph.</p>
<p>Second paragraph.</p>

the first paragraph is adjacent to the header, but the second paragraph isn't.

Thus, we can construct a rule like so:

h1 {
     margin-bottom: 0.125em;
}

h1 + p {
     margin-top: 0.125em;
}

The first rule makes the bottom margin of the h1 element very tiny. The second rule has the adjacent selector (a plus sign) to indicate that every paragraph directly proceeding an h1 element should have a tiny top margin.

Unfortunately, IE 5 is buggy with adjacent selectors, and I'm not sure what IE 6's current support status is. Every other browser should support it fine though.

 

[Shannon]

This is directed at Sage's adjacent selectors.

From Quirksmode

pre + p {font-style: italic;}

Not at all supported by Netscape 4, Explorer 5.5 and 6 on Windows and iCab. Omniweb selects the pre. Explorer 4 and 5.0 on Windows select all paragraphs.

And if we look at the April '04 W3C browser stats, 72.2% of users use IE6 and another 10.6% use IE5. That's a lot of people that get that unwanted whitespace.

 

[Sage]

You'll do anything to keep his line breaks, won't you?

 

[Shannon]

Originally posted by Sage
You'll do anything to keep his line breaks, won't you?

Well, I was actually reading through some of the selectors on Quirksmode when you posted that and I thought I may as well post up the support for it.

 

[ALPHA]

Originally posted by Sage
*bumpity bump*

[Big Snip]

The first rule makes the bottom margin of the h1 element very tiny. The second rule has the adjacent selector (a plus sign) to indicate that every paragraph directly proceeding an h1 element should have a tiny top margin.

Unfortunately, IE 5 is buggy with adjacent selectors, and I'm not sure what IE 6's current support status is. Every other browser should support it fine though.

With all that lovely insight, until XHTML 2.0 is supported by all browsers (Yes, including Internet Explorer) the simple answer would be to use <br /> tags. Right?

So to the average Joe who knows nothing about web standards and none of them do, mainly due to those dreadfully ugly page creators on geocities, tripod and all the other free web hosts why should they adapt this new method? Won't it be easier to ignore this and use <br />'s to the end of days (Not really to the end of the days but sparingly) because browsers will support <br />'s in their quirks modes, they need to support <br />'s otherwise poor Giles and many others will end up with a site that wont work.

Plus wont <br />'s be slightly more compatible? Not everything can read CSS, so until a replacement is made, Sage you’ll be seeing a lot more of your friend Mr. <br />.

I’ll try your method out in IE soon and attach the results. Interesting.

 

[Sage]

You should know by now that I never take the easy way out. I personally take it upon myself to try to do what's technically correct instead of what's easiest, just because I learn more that way. Otherwise I'd still be making table-based designs in Dreamweaver.

 

[ALPHA]

Originally posted by Sage
You should know by now that I never take the easy way out. I personally take it upon myself to try to do what's technically correct instead of what's easiest, just because I learn more that way. Otherwise I'd still be making table-based designs in Dreamweaver.

Hans Moleman says Boo 'urns to tables in Dreamweaver!