You are here:

Dreamweaver/popup images in Firefox

Advertisement


Question
I created a page in Dreamweaver CS5 and have a page with several images (http://fabserv.com/polyurethane/avery.shtml).  When the name of a fabric is clicked, it is linked to a larger image of the thumbnail shown.  In Firefox, the image is shown on a new page with a solid black background.  In IE, the background is not black.  How do I get Firefox to have a white (or other color) background around the new popup image?

Answer
Dear Marty,

These windows are controlled by a Javascript command, <a href= "javascript:<
  MM_openBrWindow('yourfile.htm',......

This page give more background about the parameters you can pass to the pop up window,  Unfortunately the background color is not one of theseparameters.
https://www.msu.edu/~urban/sme865/resources/controlling_window_size.html

Here are the results of the WC3 validation ( http://validator.w3.org/check?uri=http%3A%2F%2Ffabserv.com%2Fpolyurethane%2Faver ). Correcting these may help with your issue as well,  Good luck. I hope this helps.

Validation Output: 18 Errors

Line 4, Column 44: NET-enabling start-tag requires SHORTTAG YES
<LINK href="../includes/main.css" type=text/css rel=stylesheet>

For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Line 5, Column 49: document type does not allow element "META" here
<META content="Fabric Services" name=Description>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 6, Column 158: document type does not allow element "META" here
… polyurethane, esop, lamination, sheeting, cutting, perforating" name=Keywords>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 7, Column 73: NET-enabling start-tag requires SHORTTAG YES
…ge=JavaScript src="../includes/browserdetect.js" type=text/JavaScript></SCRIPT>

For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Line 16, Column 7: end tag for element "HEAD" which is not open
</HEAD>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 18, Column 6: document type does not allow element "BODY" here
<BODY>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 39, Column 39: there is no attribute "HEIGHT"
   <TD width=900>      <TABLE height=26 cellSpacing=0 cellPadding=0 width="100…

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.

Line 40, Column 18: there is no attribute "BACKGROUND"
     background="../images/nav_background3.jpg" border=0>

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.

Line 43, Column 19: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
       <TR align=middle>

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

Line 58, Column 157: required attribute "ALT" not specified
…v.gif" width="31" height="22" border="0" align="middle"> Polyurethane</A></TD>

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Line 87, Column 58: end tag for element "TD" which is not open
     </TR></TBODY></TABLE></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 87, Column 63: end tag for element "TR" which is not open
     </TR></TBODY></TABLE></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 87, Column 71: end tag for element "TBODY" which is not open
     </TR></TBODY></TABLE></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 87, Column 79: end tag for element "TABLE" which is not open
     </TR></TBODY></TABLE></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 88, Column 39: required attribute "ALT" not specified
     <img src="../images/divider.jpg">

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Line 121, Column 33: required attribute "ALT" not specified
<img src="../images/divider.jpg">

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Line 122, Column 4: document type does not allow element "TR" here
<TR><TD colspan="2"> </TD>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 123, Column 15: document type does not allow element "TR" here
</TR></DIV><TR>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 125, Column 35: character "%" is not allowed in the value of attribute "COLSPAN"
class=footerFinePrint colspan="100%">Copyright © 2011. All Rights

It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

Line 127, Column 18: end tag for element "TABLE" which is not open
</TD></TR></TABLE>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

↑ TOP

Best Regards,
Anna

Dreamweaver

All Answers


Answers by Expert:


Ask Experts

Volunteer


Anna Schuttenhelm

Expertise

I can answer most questions about Organic Search Engine Optimization, using CSS, research and define keyword phrases, SEO-enhanced content writing and website taxonomy which best gets the attention of the search engines. I can also answer questions pertaining to well constructed and easy to understand website programming, content writing which specifically target key word terms, how to design a website with easy to understand navigation so that your site pushes visitors through to your desired call to action such as an order form or contact form, which files to include specifically for SEO such as sitemap.xml, .htaccess, robots.txt, Google verification file and more. I can bring you insight so that, when you launch your site, it will immediately start to draw attention of the Search Engines,

Experience

I have had over 19 years experience in Marketing Communications, full spread advertising campaigns, trade show presence and coordination, website architecture and design, as well as SEO and content writing. I was personally trained by the SEO guru, Bruce Clay and also worked closely with SEO Expert, Steve Wiideman.

Publications
Please visit my website for samples of my writing, design and SEO accomplishments. seocontentplus.com . I have written articles for Business Computer Review and a cover story for Computer Networking.

Education/Credentials
I've attended the renowned two day SEO seminar presented by Bruce Clay, SEO Guru. I worked side-by-side with SEO Expert Steve Wiideman for over 8 months. I attended a week-long course on Adobe Flash with action script. I received an AA in Business Administration from a respected college in Los Angeles.

Past/Present Clients
I have written, provided SEO Consulting and/or designed websites in a multitude of industries including: Education, Wood Working Tools Industry, Health Insurance, Call Center Software, International Call Accounting Services, Document Filing Services, International Cameras Equipment, High Tech- Software, Service & Hardware, Ingredient Manufacturing, ....and more My website has links to the sites referenced about.

©2016 About.com. All rights reserved.