![]() | |
![]() |
| | Thread Tools | Display Modes |
#21
| |||
| |||
|
|
dorayme wrote: In article <m1abeeioa2.fsf (AT) dot-app (DOT) org>, Sherm Pendley <spamtrap (AT) dot-app (DOT) org> wrote: Fistro <rafaminu (AT) gmail (DOT) com> writes: On Sep 11, 4:02 pm, Ben Bacarisse <ben.use... (AT) bsb (DOT) me.uk> wrote: The server is adding elements in front of the DOCTYPE. The DOCTYPE is designed to put all browsers in "standards" rather than "quirks" mode but any text at all before it changes this behaviour. This is the code being added: It doesn't matter *what* gets added. What part of "any text at all" is not clear to you? I regularly add things like ?php $thisPage="name"; ? But that does not send that text to the browser, as with any *server-side* code. |
|
So maybe there is more to understanding "any text at all" than might seem. So to more finely define it, any text sent from the server to the browser before the DOCTYPE will cause problems... |
#22
| |||
| |||
|
|
To the OP, do you know you can get some pretty good free hosting without all this nonsense by the hosters that you are experiencing? |
#23
| |||
| |||
|
|
dorayme wrote: To the OP, do you know you can get some pretty good free hosting without all this nonsense by the hosters that you are experiencing? Already gave him the tip. Didn't seem to be too receptive, I guess he'd rather keep flogging it to see if he can get IE to fall in line. |
#24
| |||
| |||
|
|
On Sep 12, 3:22 am, "Jonathan N. Little" <lws4... (AT) central (DOT) net> wrote: dorayme wrote: To the OP, do you know you can get some pretty good free hosting without all this nonsense by the hosters that you are experiencing? Already gave him the tip. Didn't seem to be too receptive, I guess he'd rather keep flogging it to see if he can get IE to fall in line. I have already made IE fall in line. Still a few things to tune up, but I got it. I must apologize to Bacarise for my reaction and thank him and everyone else for their comments, specially those who provide me with an insight into the problem. I know it's not excuse, but I have never encountered this problem before and I just couldn't believe that on top of all the inconsistencies that IE has, there was another one that will force me to start all over again. It is true, I refused to be beaten by some "quirks mode" imposed upon me by those brainless twits at Microsoft. |
#25
| |||
| |||
|
|
Fistro wrote: On Sep 12, 3:22 am, "Jonathan N. Little" <lws4... (AT) central (DOT) net> wrote: dorayme wrote: To the OP, do you know you can get some pretty good free hosting without all this nonsense by the hosters that you are experiencing? Already gave him the tip. Didn't seem to be too receptive, I guess he'd rather keep flogging it to see if he can get IE to fall in line. I have already made IE fall in line. Still a few things to tune up, but I got it. I must apologize to Bacarise for my reaction and thank him and everyone else for their comments, specially those who provide me with an insight into the problem. I know it's not excuse, but I have never encountered this problem before and I just couldn't believe that on top of all the inconsistencies that IE has, there was another one that will force me to start all over again. It is true, I refused to be beaten by some "quirks mode" imposed upon me by those brainless twits at Microsoft. Of course you realize you have compounded your problem by trying to use XHTML what MSIE has a problem to begin with. IE behaves better, even when it is in quirks mode, with HTML then when it parses XHTML as tag soup. Do you have any specific reason for using XHTML other than "because it's advanced"? |
#26
| |||
| |||
|
|
Do you have any specific reason for using XHTML other than "because it's advanced"? Nope, no reason. It just sounds better, HTML sounds so ninetiesh ... |
#27
| |||
| |||
|
|
Fistro wrote: Do you have any specific reason for using XHTML other than "because it's advanced"? Nope, no reason. It just sounds better, HTML sounds so ninetiesh ... Well, Jukka would be quickly note: 'a mark of cluelessness' Trying XHTML, (and I mean 'trying' because your attempt is not valid XHTML) is not helping your situation. Do a little Googling and you will discover that XHTML does not have a real future at this point and HTML is far from dead. If you abandoned your attempt at XHTML and used HTML you will find that IE will cooperate will little effort on your part. |
#28
| |||
| |||
|
|
Fistro wrote: On Sep 12, 3:22 am, "Jonathan N. Little" <lws4... (AT) central (DOT) net> wrote: dorayme wrote: To the OP, do you know you can get some pretty good free hosting without all this nonsense by the hosters that you are experiencing? Already gave him the tip. Didn't seem to be too receptive, I guess he'd rather keep flogging it to see if he can get IE to fall in line. I have already made IE fall in line. Still a few things to tune up, but I got it. I must apologize to Bacarise for my reaction and thank him and everyone else for their comments, specially those who provide me with an insight into the problem. I know it's not excuse, but I have never encountered this problem before and I just couldn't believe that on top of all the inconsistencies that IE has, there was another one that will force me to start all over again. It is true, I refused to be beaten by some "quirks mode" imposed upon me by those brainless twits at Microsoft. Of course you realize you have compounded your problem by trying to use XHTML what MSIE has a problem to begin with. IE behaves better, even when it is in quirks mode, with HTML then when it parses XHTML as tag soup. |
#29
| |||
| |||
|
|
On 12 Sep, 16:34, "Jonathan N. Little" <lws4... (AT) central (DOT) net> wrote: Fistro wrote: On Sep 12, 3:22 am, "Jonathan N. Little" <lws4... (AT) central (DOT) net> wrote: dorayme wrote: To the OP, do you know you can get some pretty good free hosting without all this nonsense by the hosters that you are experiencing? Already gave him the tip. Didn't seem to be too receptive, I guess he'd rather keep flogging it to see if he can get IE to fall in line. I have already made IE fall in line. Still a few things to tune up, but I got it. I must apologize to Bacarise for my reaction and thank him and everyone else for their comments, specially those who provide me with an insight into the problem. I know it's not excuse, but I have never encountered this problem before and I just couldn't believe that on top of all the inconsistencies that IE has, there was another one that will force me to start all over again. It is true, I refused to be beaten by some "quirks mode" imposed upon me by those brainless twits at Microsoft. Of course you realize you have compounded your problem by trying to use XHTML what MSIE has a problem to begin with. IE behaves better, even when it is in quirks mode, with HTML then when it parses XHTML as tag soup. How does IE behave better when it parsers HTML as a tag soup, instead of XHTML as an HTML tag soup? I wouldn't be suprised, but do you have a reference or something? I suspect they just search for the word 'html' inside the DOCTYPE declaration, and then treat XHTML as any other HTML tag soup. Their own blogg says they are going to 'continue to read XHTML when served as “text/html”, presuming it follows the HTML compatibility recommendations'. http://blogs.msdn.com/ie/archive/2005/09/15/467901.aspx |
![]() |
| Thread Tools | |
| Display Modes | |
| |