![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| ||||
| ||||
|
|
Thanks to you all. The URL is http://pianoboe.net/ebooks/EbookTemplate03.html On the page the first line is now commented out, and is the one which gave one validation error. |
|
Below that I have inserted the suggested doctype etc from the reference Ed gave. |
|
This gives me six validation errors on the exact same HTML. So far as I can tell five of those errors refer to lines which are in the new material I just pasted in. |
|
Finally, and I expose my ignorance here, what harm will be done if I get exasperated and just go back to using the commented out doctype in the first line of the page? |
#2
| |||
| |||
|
|
Alex Bell wrote: Thanks to you all. The URL is http://pianoboe.net/ebooks/EbookTemplate03.html On the page the first line is now commented out, and is the one which gave one validation error. If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. You don't need the line beginning "<?xml version" if the encoding is UTF-8. Below that I have inserted the suggested doctype etc from the reference Ed gave. I would suggest that the whole DOCTYPE be on one line, just in case. Older versions of IE *might* mess up otherwise, though I am not certain of this. In any case, it does not hurt to put the whole DOCTYPE line on one line. This gives me six validation errors on the exact same HTML. So far as I can tell five of those errors refer to lines which are in the new material I just pasted in. Most or all of the errors are because you have two HTML tags. Dump the second HTML tag. Finally, and I expose my ignorance here, what harm will be done if I get exasperated and just go back to using the commented out doctype in the first line of the page? That will force standards mode, which is good. Thanks to you both. After I posted my previous post I went back to read |
#3
| |||
| |||
|
|
Thanks to you both. After I posted my previous post I went back to read Jukka's post in more detail, and thought about. I then spent a very frustrating hour going to the reference Ed gave me, and copying and pasting various doctypes into my page after commenting out the previous one - I didn't know about the requirement that doctype be on the first line. At least one of the doctypes required that the trailing slash in meta /> and <img /> be taken out, and some required that it be left in. This makes no sense at all to me, so I think I'll stick to ebooks. |
#4
| |||
| |||
|
|
Alex Bell wrote: Thanks to you all. The URL is http://pianoboe.net/ebooks/EbookTemplate03.html On the page the first line is now commented out, and is the one which gave one validation error. If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. |
|
You don't need the line beginning "<?xml version" if the encoding is UTF-8. Below that I have inserted the suggested doctype etc from the reference Ed gave. I would suggest that the whole DOCTYPE be on one line, just in case. |
|
Older versions of IE *might* mess up otherwise, though I am not certain of this. *In any case, it does not hurt to put the whole DOCTYPE line on one line. This gives me six validation errors on the exact same HTML. So far as I can tell five of those errors refer to lines which are in the new material I just pasted in. Most or all of the errors are because you have two HTML tags. *Dump the second HTML tag. Finally, and I expose my ignorance here, what harm will be done if I get exasperated and just go back to using the commented out doctype in the first line of the page? That will force standards mode, which is good. |
#5
| |||
| |||
|
|
On 13 juil, 20:31, C A Upsdell <cupsd... (AT) nospam (DOT) not> wrote: Alex Bell wrote: Thanks to you all. The URL is http://pianoboe.net/ebooks/EbookTemplate03.html On the page the first line is now commented out, and is the one which gave one validation error. If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. This is a bug in IE and it happens in recent versions of IE (including IE 8) as well. http://www.gtalbot.org/BrowserBugsSection/MSIE7Bugs/#bug140 http://www.gtalbot.org/BrowserBugsSection/MSIE7Bugs/#bug170 http://www.gtalbot.org/BrowserBugsSection/MSIE8Bugs/#bug99 http://www.gtalbot.org/BrowserBugsSection/MSIE8Bugs/#bug196 You don't need the line beginning "<?xml version" if the encoding is UTF-8. Below that I have inserted the suggested doctype etc from the reference Ed gave. I would suggest that the whole DOCTYPE be on one line, just in case. On one line, [preferably] without carriage returns. But the line with the doctype declaration can wrap; in fact, it usually (and very often) wraps onto the next line. 121 characters is usually well over the normal number of columns in standard text editors (or an application displaying source code). Older versions of IE *might* mess up otherwise, though I am not certain of this. In any case, it does not hurt to put the whole DOCTYPE line on one line. This gives me six validation errors on the exact same HTML. So far as I can tell five of those errors refer to lines which are in the new material I just pasted in. Most or all of the errors are because you have two HTML tags. Dump the second HTML tag. Finally, and I expose my ignorance here, what harm will be done if I get exasperated and just go back to using the commented out doctype in the first line of the page? That will force standards mode, which is good. No. Commenting the first doctype declaration which is before the xml declaration will be reported as a validation markup error and will also trigger backward-compatible "quirks" rendering mode in IE 8. And this is not reasonable here. Again, best would be to go with HTML 4 Strict as Ed Mullen suggested. regards, Gérard -- Internet Explorer 7 bugs: 178 bugs so far http://www.gtalbot.org/BrowserBugsSection/MSIE7Bugs/ Internet Explorer 8 bugs: 53 bugs so far http://www.gtalbot.org/BrowserBugsSection/MSIE8Bugs/ |
#6
| |||
| |||
|
|
If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. This is a bug in IE and it happens in recent versions of IE (including IE 8) as well. |
#7
| |||
| |||
|
|
In article 4a10ec3c-c4ce-4327-92f3-089e4d44a26e...oglegroups.com>, GTalbot <newsgroup (AT) gtalbot (DOT) org> wrote: If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. This is a bug in IE and it happens in recent versions of IE (including IE 8) as well. Is this bug something that many people knew and talked about before and during the time that IE8 was being developed? |
|
Is the development of IE8 done in some sort of deep underground bunker somewhere with limited connections to the outside world? |
#8
| |||
| |||
|
|
dorayme wrote: In article 4a10ec3c-c4ce-4327-92f3-089e4d44a26e...oglegroups.com>, GTalbot <newsgroup (AT) gtalbot (DOT) org> wrote: If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. This is a bug in IE and it happens in recent versions of IE (including IE 8) as well. Is this bug something that many people knew and talked about before and during the time that IE8 was being developed? Yes. Is the development of IE8 done in some sort of deep underground bunker somewhere with limited connections to the outside world? Yes. |
#9
| |||
| |||
|
|
If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. This is a bug in IE and it happens in recent versions of IE (including IE 8) as well. Is this bug something that many people knew and talked about before and during the time that IE8 was being developed? Is the development of IE8 done in some sort of deep underground bunker somewhere with limited connections to the outside world? |
#10
| |||
| |||
|
|
In article 4a10ec3c-c4ce-4327-92f3-089e4d44a... (AT) o6g2000yqj (DOT) googlegroups.com>, GTalbot <newsgr... (AT) gtalbot (DOT) org> wrote: If the DOCTYPE is not on the first line, older versions of IE will render the page in quirks mode. This is a bug in IE and it happens in recent versions of IE (including IE 8) as well. Is this bug something that many people knew and talked about before and during the time that IE8 was being developed? |
|
Is the development of IE8 done in some sort of deep underground bunker somewhere with limited connections to the outside world? |
![]() |
| Thread Tools | |
| Display Modes | |
| |