Preferred Member
joined:Nov 10, 2005
posts:387
votes: 0
@BoLAN - I tend to agree; this only came up because of the conditional comment problems.
@DrDoc: concoms targeting IE work fine, but non-IE concoms cause strange URI requests to go to the server. I've tried 3 formats, all with the same results:
<![if !IE]>
THIS IS NOT IE
<![endif]>
<!--[if !IE]>-->
THIS IS NOT IE
<!--<![endif]-->
<!--[if !IE]><!-->
THIS IS NOT IE
<!--<![endif]-->
Code inside the comments is:
<link rel="stylesheet" href="/includes/non-IE.css" type="text/css" media="all" />
The error is a bad URI request and "page could not be found"; the URI varies depending on the rest of the code on the page, but invariably begins with "/inc" (the first 4 chars of my stylesheet path). That's followed by anywhere from 1-25 chars from the rest of the page, with spaces & <tags> URL-encoded. These chars often, but not always, start at a logical break in my code (e.g. a tag, =, or "), though sometimes they start completely randomly in the middle of a word, then continue until it hits either a " or a > not preceded by a slash (i.e. />, as in <br />). Here are some sample errors:
/inc=
/ince=
/inccript (from tag <script>)
/include%3Cspan%20class= ( /include<span class= )
/inctoggleClass(
Sometimes the chars are in the <head> code, sometimes in <body>. Here are some of the longest (w/o the URL-encoding):
/include<br /><br /><br /><img class=
/incOn === 2) return;(isOn < 2) ? isOn++ : isOn = 0;switch(isOn) {case 1:sets = {animation: 3, easing:
That's from a js fn, stopping at: "
This one may give some clues:
/inc-- Full-Column start --><div class=
That's the only time it didn't stop at >, probably because it reads as a comment tag.
It's obvious that it's mangling the concom code, but for I see no logic as to where it starts up after those first 4 chars. Sometimes it's way down the page.
As I said, it usually starts with /inc, but once it was:
/ine=
My page header is:
<!doctype html>
<html lang=en-US>
<head>
<Meta http-equiv="X-UA-Compatible" content="IE=Edge" />
<Meta http-equiv="Content-type" content="text/html; charset=utf-8" />
I'm using the utf-8 char set but I don't see why that should be an issue.
I've googled this and can't seem to find the issue anywhere else.
Bet you're sorry you asked!
[edited by: phranque at 11:27 pm (utc) on Jul 30, 2013]
[edit reason] disable graphic smileys [/edit]