Preserved Topic: XHTML 1.1 - strict (Page 1 of 1) $Pages that link to <a href="https://ozoneasylum.com/backlink?for=18518" title="Pages that link to Preserved Topic: XHTML 1.1 - strict (Page 1 of 1)" rel="nofollow" >Preserved Topic: XHTML 1.1 - strict <span class="small">(Page 1 of 1)</span>\$

u-neek Bipolar (III) Inmate From: Berlin, Germany Insane since: Jan 2001	posted 01-04-2002 02:51 Ok, here is my website and i want to know why the w3c validator displays error messages... I cannot find the reason. Just click the XHTML 1.1 link at the bottom right. Btw, can you check that page in any available browser - not NN 4.xx please -? Because I only use Mozilla and IE 6.0. Thanks. Edit: BTW, anybody knows a solution for <a href="blabla.html" target="_blank">blabla</a> think? That didn't work in XHTML 1.1. [This message has been edited by u-neek (edited 01-04-2002).]
warjournal Maniac (V) Mad Scientist From: Insane since: Aug 2000	posted 01-04-2002 03:34 Looks good in Opera 5. Don't know much about the CSS errors.
Emperor Maniac (V) Mad Scientist with Finglongers From: Cell 53, East Wing Insane since: Jul 2001	posted 01-04-2002 03:46 u-neek: I can only suggest you try spaces or new lines (I'm not sure why most of those errors occur - it may be something in the spec: Check out briggl's tutorial at GN pos.??). For the other problem find the HTML special character for underscore and use that - I think. Again check the specs - that must be mentioned. Emps You're my wife now Dave
warjournal Maniac (V) Mad Scientist From: Insane since: Aug 2000	posted 01-04-2002 03:54 I got it, but I can't explain it. Put your input tags in a p tag. <form....> <p> <input...> <input...> </p> </form> I kind of understand why this is, but I kind of don't. Even if I did understand this explicitly, I don't think I could explain it. I ran into this exact same problem some time ago, but I had a lapse. As I got to poking around, it hit me. I just love having Opera around for right click > Document > Validate. [This message has been edited by warjournal (edited 01-04-2002).]
rhun Nervous Wreck (II) Inmate From: Colorado Springs, CO, USA Insane since: Nov 2001	posted 01-04-2002 04:17 First thing I want to ask is why you are using strict? This page would be fine as transitional. Use this as your basic setup (this is my default template): <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title></title> </head> <body> </body> </html> Unless, of course, you feel driven to have a strict xhtml page. Which is, well, strict. "The key to discovery lies not in mathematics, but in imagination." [This message has been edited by rhun (edited 01-04-2002).]
u-neek Bipolar (III) Inmate From: Berlin, Germany Insane since: Jan 2001	posted 01-04-2002 11:22 rhun: Of course i want to have a strict XHTML 1.1 page. warjournal: Thanks for helping me solving the problem. Isn't that curious? Emperor: Underscore that link instead of using target="_blank"?
Emperor Maniac (V) Mad Scientist with Finglongers From: Cell 53, East Wing Insane since: Jul 2001	posted 01-04-2002 15:35 u-neek: I'm not sure I understand your reply (slow Emperor) but what I meant was something like: code: target="_blank"? [edit: OK that doesn't show up - I've used the HTML special character: & # 9 5 ; so remove the spaces to get it to work] I know that you have to be careful when doing links like something.php?something=12&something_else=14 but see if that helps. Emps You're my wife now Dave [This message has been edited by Emperor (edited 01-04-2002).]
u-neek Bipolar (III) Inmate From: Berlin, Germany Insane since: Jan 2001	posted 01-04-2002 17:42 Emperor, the target-think is not allowed in XHTML 1.1 anymore...
warjournal Maniac (V) Mad Scientist From: Insane since: Aug 2000	posted 01-04-2002 18:28 It's been a long time since i've dealt with frames, but isn't that allowable with the frameset DTD? I've also been looking for a layman's explaination on the difference between block element and inline. I've got a few leads, but nothing layman enough.
Emperor Maniac (V) Mad Scientist with Finglongers From: Cell 53, East Wing Insane since: Jul 2001	posted 01-04-2002 21:47 u-neek: Ahh I see. Try using JavaScript. I've been fiddling with something similar for IFRAMEs and something along the lines of parent.frames[FRAMENAME].location.href=URL should work although it doesn't seem to work with Op5. wj: It depends on how lay your man is. The specs are good: www.w3.org/TR/REC-CSS2/visuren.html#box-gen I prefer to think of them as the difference between DIVs and SPANs which can be made to act like each other by making them inline and block. I'm sure there is a clearer explanantion somewhere. Emps You're my wife now Dave
warjournal Maniac (V) Mad Scientist From: Insane since: Aug 2000	posted 01-05-2002 04:03 Heh. Yeah, I've got the W3C docs on my harddrive. Not quite layman enough for me. My light just hasn't gone on yet. I don't know the differences between div and span, so that doesn't help me either. I can get work done, but I'm still feeling my way around in the dark.
Emperor Maniac (V) Mad Scientist with Finglongers From: Cell 53, East Wing Insane since: Jul 2001	posted 01-05-2002 20:42 wj: I thought you might have the specs but it was worth a go. How about: Blocks (like DIVs) create a new line at their end. Inline elements (like SPAN) don't disrupt the flow of the page. Try a sample page with some SPANs in it and then use a crude style sheet to add: span { display: block; } and see what the changes are. I'm sure there are more fancy things that I can't think of at the moment but that is the big important details (hopefully). Emps You're my wife now Dave
warjournal Maniac (V) Mad Scientist From: Insane since: Aug 2000	posted 01-05-2002 20:55 I think I'm starting to really get it. For example: <em> <p> </p> </em> Will generate and error since p is block and em in inline. Correct?
Emperor Maniac (V) Mad Scientist with Finglongers From: Cell 53, East Wing Insane since: Jul 2001	posted 01-06-2002 20:59 wj: That is, sort of, my understanding. It would be awfully tempting to, e.g., make a couple of paragraphs bold by wrapping them in bold tags but it would be, strictly, wrong. I've seen designs where people open a font tag after the body tag and close it at the end - it will work in some browsers but is 'wrong' and thankfully CSS pretty much removes that temptation. Emps
u-neek Bipolar (III) Inmate From: Berlin, Germany Insane since: Jan 2001	posted 01-23-2002 23:33 Sorry for bumping this, but i'd like to let you know that i found a solution for targeting a new window without sacrificing the strict XHTML 1.1: <a href="blabla.html" onclick="window.open(this.href,'_blank');return false;">new win</a> [This message has been edited by u-neek (edited 01-23-2002).]
Slime Lunatic (VI) Mad Scientist From: Massachusetts, USA Insane since: Mar 2000	posted 01-24-2002 05:14 Ummm... I'm pretty sure target="" is allowed in A tags in XHTML. [This message has been edited by Slime (edited 01-24-2002).]
u-neek Bipolar (III) Inmate From: Berlin, Germany Insane since: Jan 2001	posted 01-24-2002 09:28 No, not in XHTML 1.0 Strict, in Transitional or Frameset it is allowed. The newest version XHTML 1.1 has neither Transitional nor Frameset. [This message has been edited by u-neek (edited 01-24-2002).]
mr.maX Maniac (V) Mad Scientist From: Belgrade, Serbia Insane since: Sep 2000	posted 01-24-2002 22:12 Actually, new specification XHTML 1.1 is module based, so if you need frames you simply add XHTML Frames module...

Preserved Topic: XHTML 1.1 - strict (Page 1 of 1) $Pages that link to <a href="https://ozoneasylum.com/backlink?for=18518" title="Pages that link to Preserved Topic: XHTML 1.1 - strict (Page 1 of 1)" rel="nofollow" >Preserved Topic: XHTML 1.1 - strict <span class="small">(Page 1 of 1)</span>\$

u-neek
Bipolar (III) Inmate

From: Berlin, Germany
Insane since: Jan 2001

posted 01-04-2002 02:51

Ok, here is my website and i want to know why the w3c validator displays error messages... I cannot find the reason. Just click the XHTML 1.1 link at the bottom right.

Btw, can you check that page in any available browser - not NN 4.xx please -? Because I only use Mozilla and IE 6.0.

Thanks.

Edit: BTW, anybody knows a solution for <a href="blabla.html" target="_blank">blabla</a> think? That didn't work in XHTML 1.1.

[This message has been edited by u-neek (edited 01-04-2002).]

warjournal
Maniac (V) Mad Scientist

From:
Insane since: Aug 2000

posted 01-04-2002 03:34

Looks good in Opera 5.

Don't know much about the CSS errors.

Emperor
Maniac (V) Mad Scientist with Finglongers

From: Cell 53, East Wing
Insane since: Jul 2001

posted 01-04-2002 03:46

u-neek: I can only suggest you try spaces or new lines (I'm not sure why most of those errors occur - it may be something in the spec: Check out briggl's tutorial at GN pos.??).

For the other problem find the HTML special character for underscore and use that - I think. Again check the specs - that must be mentioned.

Emps

You're my wife now Dave

warjournal
Maniac (V) Mad Scientist

From:
Insane since: Aug 2000

posted 01-04-2002 03:54

I got it, but I can't explain it.

Put your input tags in a p tag.

<form....>
<p>
<input...>
<input...>
</p>
</form>

I kind of understand why this is, but I kind of don't. Even if I did understand this explicitly, I don't think I could explain it. I ran into this *exact* same problem some time ago, but I had a lapse. As I got to poking around, it hit me. I just love having Opera around for right click > Document > Validate.

[This message has been edited by warjournal (edited 01-04-2002).]

rhun
Nervous Wreck (II) Inmate

From: Colorado Springs, CO, USA
Insane since: Nov 2001

posted 01-04-2002 04:17

First thing I want to ask is why you are using strict? This page would be fine as transitional. Use this as your basic setup (this is my default template):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title></title>
</head>
<body>
</body>
</html>

Unless, of course, you feel driven to have a strict xhtml page. Which is, well, strict.

"The key to discovery lies not in mathematics, but in imagination."

[This message has been edited by rhun (edited 01-04-2002).]

u-neek
Bipolar (III) Inmate

From: Berlin, Germany
Insane since: Jan 2001

posted 01-04-2002 11:22

rhun: Of course i want to have a strict XHTML 1.1 page.

warjournal: Thanks for helping me solving the problem. Isn't that curious?

Emperor: Underscore that link instead of using target="_blank"?

Emperor
Maniac (V) Mad Scientist with Finglongers

From: Cell 53, East Wing
Insane since: Jul 2001

posted 01-04-2002 15:35

u-neek: I'm not sure I understand your reply (slow Emperor) but what I meant was something like:

code:

target="&#95;blank"?

[edit: OK that doesn't show up - I've used the HTML special character: & # 9 5 ; so remove the spaces to get it to work]

I know that you have to be careful when doing links like something.php?something=12&something_else=14 but see if that helps.

Emps

You're my wife now Dave

[This message has been edited by Emperor (edited 01-04-2002).]

u-neek
Bipolar (III) Inmate

From: Berlin, Germany
Insane since: Jan 2001

posted 01-04-2002 17:42

Emperor, the target-think is not allowed in XHTML 1.1 anymore...

warjournal
Maniac (V) Mad Scientist

From:
Insane since: Aug 2000

posted 01-04-2002 18:28

It's been a long time since i've dealt with frames, but isn't that allowable with the frameset DTD?

I've also been looking for a layman's explaination on the difference between block element and inline. I've got a few leads, but nothing layman enough.

Emperor
Maniac (V) Mad Scientist with Finglongers

From: Cell 53, East Wing
Insane since: Jul 2001

posted 01-04-2002 21:47

u-neek: Ahh I see. Try using JavaScript. I've been fiddling with something similar for IFRAMEs and something along the lines of parent.frames[FRAMENAME].location.href=URL should work although it doesn't seem to work with Op5.

wj: It depends on how lay your man is. The specs are good:
www.w3.org/TR/REC-CSS2/visuren.html#box-gen

I prefer to think of them as the difference between DIVs and SPANs which can be made to act like each other by making them inline and block. I'm sure there is a clearer explanantion somewhere.

Emps

You're my wife now Dave

warjournal
Maniac (V) Mad Scientist

From:
Insane since: Aug 2000

posted 01-05-2002 04:03

Heh. Yeah, I've got the W3C docs on my harddrive. Not quite layman enough for me. My light just hasn't gone on yet. I don't know the differences between div and span, so that doesn't help me either. I can get work done, but I'm still feeling my way around in the dark.

Emperor
Maniac (V) Mad Scientist with Finglongers

From: Cell 53, East Wing
Insane since: Jul 2001

posted 01-05-2002 20:42

wj: I thought you might have the specs but it was worth a go. How about:

Blocks (like DIVs) create a new line at their end.

Inline elements (like SPAN) don't disrupt the flow of the page.

Try a sample page with some SPANs in it and then use a crude style sheet to add: span { display: block; } and see what the changes are.

I'm sure there are more fancy things that I can't think of at the moment but that is the big important details (hopefully).

Emps

You're my wife now Dave

warjournal
Maniac (V) Mad Scientist

From:
Insane since: Aug 2000

posted 01-05-2002 20:55

I think I'm starting to really get it. For example:

<em>
<p>
</p>
</em>

Will generate and error since p is block and em in inline.
Correct?

Emperor
Maniac (V) Mad Scientist with Finglongers

From: Cell 53, East Wing
Insane since: Jul 2001

posted 01-06-2002 20:59

wj: That is, sort of, my understanding. It would be awfully tempting to, e.g., make a couple of paragraphs bold by wrapping them in bold tags but it would be, strictly, wrong. I've seen designs where people open a font tag after the body tag and close it at the end - it will work in some browsers but is 'wrong' and thankfully CSS pretty much removes that temptation.

Emps

u-neek
Bipolar (III) Inmate

From: Berlin, Germany
Insane since: Jan 2001

posted 01-23-2002 23:33

Sorry for bumping this, but i'd like to let you know that i found a solution for targeting a new window without sacrificing the strict XHTML 1.1:

<a href="blabla.html" onclick="window.open(this.href,'_blank');return false;">new win</a>

[This message has been edited by u-neek (edited 01-23-2002).]

Slime
Lunatic (VI) Mad Scientist

From: Massachusetts, USA
Insane since: Mar 2000

posted 01-24-2002 05:14

Ummm... I'm pretty sure target="" is allowed in A tags in XHTML.

[This message has been edited by Slime (edited 01-24-2002).]

u-neek
Bipolar (III) Inmate

From: Berlin, Germany
Insane since: Jan 2001

posted 01-24-2002 09:28

No, not in XHTML 1.0 Strict, in Transitional or Frameset it is allowed. The newest version XHTML 1.1 has neither Transitional nor Frameset.

[This message has been edited by u-neek (edited 01-24-2002).]

mr.maX
Maniac (V) Mad Scientist

From: Belgrade, Serbia
Insane since: Sep 2000

posted 01-24-2002 22:12

Actually, new specification XHTML 1.1 is module based, so if you need frames you simply add XHTML Frames module...