Hi I'm in the process of designing this site for a new client and was wondering if anyone here could help me with this fix please? Its a flash header and on each page change it all seems to jump (well it does on mine anyway) - in IE its fine? http://rani.webcity.com.au/~pen49050/index.html Any advice is extremely welcome Rachelle
Validate your html for that list of 18 errors. The most important ones might be unclosed tags and xml processing errors.
Will do - sorry I hadn't even looked at doing that! Assumed it was a flash / Firefox error and was going to validate afterwards!! Thanks
I'm down to 5 errors now but they're all related to the embedded flash - all I've done is create the flash in CS3 and then imported it to DW CS3? Any advice please with these errors would be great This is the line that its not happy with: <embed src="images/penair.swf" quality="high" pluginspage="http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash"></embed> Giving these errors: 1. Error Line 23, Column 15: there is no attribute "src". <embed src="images/penair.swf" quality="high" pluginspage="http://www.adobe. ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 2. Error Line 23, Column 43: there is no attribute "quality". …mbed src="images/penair.swf" quality="high" pluginspage="http://www.adobe.com ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 3. Error Line 23, Column 62: there is no attribute "pluginspage". …nair.swf" quality="high" pluginspage="http://www.adobe.com/shockwave/download ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 4. Error Line 23, Column 153: there is no attribute "type". …P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash"></embed> ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 5. Error Line 23, Column 184: element "embed" undefined. … type="application/x-shockwave-flash"></embed> ✉ You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
The "jump" is due to going from a page that overflows vertically to one that doesn't, and vice versa. IE always has the scrollbar in place. Firefox adds one when needed. If this truly bothers you, add html {height: 100.1%;}. That will force a scrollbar on every page. The embed element is not a part of html. Mark it up like so: <div id="header"> <!--[if ie]> <script type="text/javascript"> //<![CDATA[ AC_FL_RunContent( 'codebase','http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,14,0','width','770','height','170','title','Peninsula Air Conditioning NSW','src','images/penair','quality','high','pluginspage','http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash','movie','images/penair' ); //end AC code //]]> </script> <noscript><object classid= "clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase= "http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,14,0" width="770" height="170" title="Peninsula Air Conditioning NSW"> <param name="movie" value="images/penair.swf" /> <param name="quality" value="high" /> </object></noscript> <![endif]--> <!--[if !ie]--> <object type="application/x-shockwave-flash" data="http://rani.webcity.com.au/~pen49050/images/penair.swf" width="770" height="170"> <p><img src="images/penair.png" alt="Peninsula Air Conditioning" height="170" width="770" /></p> </object> <!--[/endif]--> </div> Code (markup): cheers, gary
OK i've tried the 100.1% thing and it still seems that the page goes blank when loading each page? I'll try the new code for the flash and see if that makes a difference. Thanks again
Goes blank? Not here. You may need to increase the size a bit, if 100.1% doesn't force the scrollbar. 100.5% should be the maximum needed size. cheers, gary