| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| Hi i have a No script tag with a http redirect, but my page will not validate to w3c is there a way to check the clients javascript using server side? or a better way to handle the no script? |
|
#2
| |||
| |||
| The problem must be caused by something else. The http://www.w3.org/TR/html401/interac...#edef-NOSCRIPT complies with the latest W3C specification. |
|
#3
| |||
| |||
| the noscript tag is fine, its whats inside the tag what the best way to redirect to another cfm page inside the noscript tag |
|
#4
| |||
| |||
| <NOSCRIPT> <meta HTTP-EQUIV="Refresh" CONTENT="0; URL=http://www.myOtherWebSite.com"> </NOSCRIPT> |
|
#5
| |||
| |||
| ok thats what i had but i get w3c error document type does not allow element "META" here. i have it ion my head tag? |
|
#6
| |||
| |||
| I can see the dilemma. It is generally expected that <meta> will be within the head and <noscript> within the body. So where do you place the combination of <noscript> and >meta>? I would place the tags where they produce the result I want, namely, in the head, where the script tag usually is, and accept the w3c error for what it is. Your requirement that the noscript tag do a redirect may actually be self-contradictory. At least, that is my opinion. The noscript tag is designed to provide alternative content -- for the current page, I would assume -- when the script tag is not executed. |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.