hkwebsite 寫:
<frameset cols="80,*" frameborder="no" border="0" framespacing="0">
frameborder="no" border="0" framespacing="0">
不能通過w3c,怎樣改呢?
Below are the results of attempting to parse this document with an SGML parser.
1.
Line 8, column 15: there is no attribute "COLS"
<frameset cols="80,*" frameborder="no" border="0" framespacing="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.
✉
2.
Line 8, column 34: there is no attribute "FRAMEBORDER"
<frameset cols="80,*" frameborder="no" border="0" framespacing="0">
✉
3.
Line 8, column 46: there is no attribute "BORDER"
<frameset cols="80,*" frameborder="no" border="0" framespacing="0">
✉
4.
Line 8, column 63: there is no attribute "FRAMESPACING"
... cols="80,*" frameborder="no" border="0" framespacing="0">
✉
5.
Line 8, column 66: element "FRAMESET" undefined
..."80,*" frameborder="no" border="0" framespacing="0">
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), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
6.
Line 9, column 11: there is no attribute "SRC"
<frame src="left.htm" name="leftFrame" scrolling="NO" noresize>
✉
7.
Line 9, column 27: there is no attribute "NAME"
<frame src="left.htm" name="leftFrame" scrolling="NO" noresize>
✉
8.
Line 9, column 49: there is no attribute "SCROLLING"
<frame src="left.htm" name="leftFrame" scrolling="NO" noresize>
✉
9.
Line 9, column 62: "NORESIZE" is not a member of a group specified for any attribute
...src="left.htm" name="leftFrame" scrolling="NO" noresize>
✉
10.
Line 9, column 62: element "FRAME" undefined
...src="left.htm" name="leftFrame" scrolling="NO" noresize>
✉
11.
Line 10, column 39: element "FRAME" undefined
<frame src="right.htm" name="mainFrame">
✉
12.
Line 12, column 10: end tag for element "FRAMESET" which is not open
</frameset>
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 occured in a script section of your document, you should probably read this FAQ entry.
✉
13.
Line 13, column 15: document type does not allow element "BODY" here
<noframes><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).
登入
註冊
問答集
搜尋
