| Not logged in - | |
| Not logged in - | |
The new pages are almost completed and have pricing/leasing info for UltraBB
V 1.17. Hope to see you there! |
| Moderated by: Jim |
|
||||||||||||||
| Order of blocks in Ultra look - Troubleshooting - UltraBB - UltraBB Forums | |||||||||||||||
| Author | Post | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
mwk-empire Member 
|
Hi, the order of the blocks (e.g. the footer is not at the bottom) in the ultra design are wrong in the Opera and Safari browsers. Not an urgent problem but probably easy to fix. Best Markus Attachment: order.jpg (Downloaded 31 times)
|
||||||||||||||
| |||||||||||||||
| |||||||||||||||
|
Jim Administrator 
|
Hmmm I didn't check it in opera (less than 1.5% overall use) and I can't check it in safari. Does it look the same in both those browsers? It was tested extensively in IE and Firefox which is what over 95% of people use. I wish I could see it in safari because I have respect for Mac's. I'll try Opera later tonight and see if there is something quick I can do.
|
||||||||||||||
| |||||||||||||||
| |||||||||||||||
|
mwk-empire Member
|
Hi Jim, yes, it looks the same in Safari and Opera. You can use Safari on Windows (this is what I did for the shot). It is still beta but works pretty well. Best Markus
|
||||||||||||||
| |||||||||||||||
| |||||||||||||||
|
Jim Administrator
|
OK I'll look for it. I know you can use Firefox in KDE on linux also but it doesn't respond to HTML identically to the windows version.
|
||||||||||||||
| |||||||||||||||
| |||||||||||||||
|
mwk-empire Member
|
I made a quick check with the CSE HTML Validator. It reports that there are nested TD tags. And there also table nesting problems. It might be that Opera and Safari are a little bit more critical than IE and FireFox. Here is the report: Validator message export for "http://www.wowultra.com/forum/": Generated by CSE HTML Validator Professional v8.04 (http://www.htmlvalidator.com/) 1. Message: (Accessibility->Web Content Accessibility Guidelines 1.0) [73] WCAG 1.0 accessibility checking is disabled. 2. Message: (Accessibility->Section 508 Accessibility Standards) [73] Section 508 accessibility checking is disabled. 3. Message in line 7 at character 2: (Grouped->Search Engine) Tip - A good title is very important for search engine listings. Use many keywords and search terms in the title but make it readable. Don't just stuff keywords in the title. The title should also be something that a user will want to click on when it's listed on a search engine. A good title is also important when a visitor bookmarks a page. Example: Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows. AI Internet Solutions also recommends that the "title" tag be the first tag inside the "head" section. 4. Message in line 7 at character 18: (Grouped->Search Engine) [8] This document's title contains only 2 words. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase. The title should also contain keywords and search terms while remaining readable. 5. Message in line 242 at character 2: (Grouped->Deprecated) [9] Even though the "center" element is deprecated in HTML 4.01 and XHTML, real-world circumstances may make using this element better than using CSS in some situations. Using CSS may be more complex and may not easily (or at all) give the desired effect of centering blocks like forms and tables. However, AI Internet Solutions still recommends using CSS whenever reasonably possible. 6. Message in line 242 at character 2: (Grouped->Deprecated) [9] The "center" element is deprecated in HTML 4.01 and XHTML in favor of using style sheets (to center text use the CSS "text-align: center" instead or align="center" where "align" is not deprecated). Another option is to use ... instead of ..., but this may not center tables. The "center" element may become obsolete and unsupported in the future. 7. Message in line 243 at character 2: (Grouped->General Compatibility) The "table" tag is contained in a "center" tag. Different browsers may render this very differently. For example, Internet Explorer 6.0 may center the table cell content (depending on the DOCTYPE) while Internet Explorer 5.5 does not. However, both will center the table itself. If you want to center the table, then align="center" may be used in the "table" tag. 8. Message in line 243 at character 2: (Grouped->General Compatibility) [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element. 9. Error in line 244 at character 32: The "align" attribute has an invalid attribute value "middle". Try using one of the following values: "center", "char", "justify", "left", or "right". 10. Message in line 244 at character 40: (Grouped->Deprecated) [9] The "height" and "width" attributes for the "td" and "th" elements are deprecated in HTML 4.01 and XHTML in favor of using style sheets. 11. Message in line 244 at character 71: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "img" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 12. Error in line 245 at character 30: The "align" attribute has an invalid attribute value "middle". Try using one of the following values: "center", "char", "justify", "left", or "right". 13. Message in line 245 at character 44: (Grouped->General Compatibility) HTML 4.01 and XHTML allow the "name" attribute with the "form" element for backward compatibility. However, the "id" attribute should be used to identify elements. Previously, HTML 4.0 did not allow the "name" attribute with the "form" element. It is recommended that both "name" and "id" attributes be used when using the "form" element. The values for both of these attributes should be identical. 14. Message in line 247 at character 2: (Grouped->General Compatibility) The "table" tag is contained in a "center" tag. Different browsers may render this very differently. For example, Internet Explorer 6.0 may center the table cell content (depending on the DOCTYPE) while Internet Explorer 5.5 does not. However, both will center the table itself. If you want to center the table, then align="center" may be used in the "table" tag. 15. Message in line 247 at character 2: (Grouped->Good Style) Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute. 16. Message in line 249 at character 115: (Grouped->General Compatibility) [5] The "background" attribute for the "td" and "th" elements is not an official HTML or XHTML attribute and is only supported by Internet Explorer 3.0+ and Netscape 4.0+. Other browsers may not support this attribute. For instance, Netscape 3.0 does not support this attribute. 17. Message in line 249 at character 178: (Grouped->Tips) [6] Using the "nowrap" attribute can create extremely wide cells and can produce unusual results. It can also cause a page to have to be horizontally scrolled. Be careful when using this attribute. 18. Message in line 249 at character 178: (Grouped->Deprecated) [9] The "nowrap" attribute for the "td" and "th" elements is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Consider using the CSS "white-space: nowrap" instead of the "nowrap" attribute. Note, however, there are issues with the "white-space" property and using the deprecated "nowrap" attribute probably works best. 19. Message in line 262 at character 60: (Grouped->Good Style) The "strong" element should be used instead of the "b" element when you want to denote strong emphasis. The "b" element should only be used when you want bold typeface but do not want strong emphasis. Many web authors use the "b" element when the "strong" element would be more appropriate. 20. Message in line 266 at character 2: (Grouped->Good Style) Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute. 21. Error in line 273 at character 2: The "td" element cannot be used here. It is nested in another "td" tag and cannot be nested. Has the previous "td" element been ended? This element may be contained in "tr". This element may not be contained in "td" and "th". 22. Error in line 273 at character 94: The "TD" element cannot be used here. It is nested in another "TD" tag and cannot be nested. Has the previous "TD" element been ended? This element may be contained in "tr". This element may not be contained in "td" and "th". 23. Error in line 273 at character 282: The "TD" element cannot be used here. It is nested in another "TD" tag and cannot be nested. Has the previous "TD" element been ended? This element may be contained in "tr". This element may not be contained in "td" and "th". 24. Error in line 276 at character 65: The "br" element cannot be used here. It is contained in a "table" tag that cannot contain it. This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "table". 25. Message in line 276 at character 2: (Grouped->General Compatibility) The "table" tag is contained in a "center" tag. Different browsers may render this very differently. For example, Internet Explorer 6.0 may center the table cell content (depending on the DOCTYPE) while Internet Explorer 5.5 does not. However, both will center the table itself. If you want to center the table, then align="center" may be used in the "table" tag. 26. Error in line 278 at character 897: The hexadecimal color value for the "color" attribute is missing the '#' character. Use color="#FF0000". 27. Warning in line 278 at character 988: [64] An invalid character reference was found in the "HREF" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 28. Error in line 278 at character 1871: The hexadecimal color value for the "color" attribute is missing the '#' character. Use color="#006600". 29. Warning in line 278 at character 1965: [64] An invalid character reference was found in the "HREF" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 30. Error in line 278 at character 2118: The "center" element cannot be used here. It is contained in a "table" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". 31. Message in line 278 at character 110: (Styles->General) The "style" attribute has been used but a default style sheet language has not been defined (note that HTML Validator would not see this declaration if it is sent as an HTTP header by a web server). HTML 4.01 and XHTML require this for correct documents. However, for all practical purposes, leaving it out is very unlikely to cause problems. If you still want to define a default style sheet language, then include this in the "head" section of your document to specify "text/css" as the default style sheet language: . If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. Because this issue is very unlikely to cause problems, consider ignoring or disabling this message. See http://www.w3.org/TR/html4/present/styles.html#default-style for more information. 32. Message in line 278 at character 110: (Styles->CSS Tips) Use the inline "style" attribute sparingly. Using this attribute too often can prevent you from receiving many of the benefits of CSS like easier to maintain and less cluttered documents. Consider using a single CSS style sheet instead of relying too much on the "style" attribute. This message is displayed only once. 33. Message in line 278 at character 885: (Grouped->Deprecated) [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the "color", "font", "font-family", "font-size", and other CSS font properties instead). 34. Message in line 278 at character 1047: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "IMG" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 35. Message in line 278 at character 2024: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "IMG" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 36. Error in line 279 at character 2: The "table" element cannot be used here. It is nested in another "table" tag and cannot be nested. Has the previous "table" element been ended? This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". 37. Error in line 279 at character 65: The "br" element cannot be used here. It is contained in a "table" tag that cannot contain it. This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "table". 38. Error in line 281 at character 918: The hexadecimal color value for the "color" attribute is missing the '#' character. Use color="#006600". 39. Warning in line 281 at character 1018: [64] An invalid character reference was found in the "HREF" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 40. Error in line 281 at character 1880: Found an ampersand '&' but could not find a following semicolon for a properly formed character reference. If you want to actually display an ampersand, such as in "Recreation & Sports", then use the character entity reference "&" as in "Recreation & Sports" (see comment). 41. Error in line 281 at character 2239: The hexadecimal color value for the "color" attribute is missing the '#' character. Use color="#006600". 42. Warning in line 281 at character 2347: [64] An invalid character reference was found in the "HREF" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 43. Error in line 281 at character 3227: The hexadecimal color value for the "color" attribute is missing the '#' character. Use color="#FF0000". 44. Warning in line 281 at character 3312: [64] An invalid character reference was found in the "HREF" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 45. Error in line 281 at character 3465: The "center" element cannot be used here. It is contained in a "table" tag that cannot contain it. This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". 46. Message in line 281 at character 1077: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "IMG" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 47. Message in line 281 at character 2406: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "IMG" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 48. Message in line 281 at character 3371: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "IMG" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 49. Error in line 282 at character 2: The "table" element cannot be used here. It is nested in another "table" tag and cannot be nested. Has the previous "table" element been ended? This element may be contained in "body", "dd", "td", and "th". This element may not be contained in "dl" and "table". 50. Error in line 282 at character 65: The "br" element cannot be used here. It is contained in a "table" tag that cannot contain it. This element may be contained in "body", "caption", "td", and "th". This element may not be contained in "table". 51. Error in line 284 at character 940: The hexadecimal color value for the "color" attribute is missing the '#' character. Use color="#FF0000". 52. Warning in line 284 at character 1043: [64] An invalid character reference was found in the "HREF" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 53. Error in line 284 at character 1935: The hexadecimal color value for the "color" attribute is missing the '#' character. Use color="#FF0000". 54. Warning in line 284 at character 2047: [64] An invalid character reference was found in the "HREF" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 55. Error in line 284: Terminating validation due to too many errors. Please correct the previous errors and recheck the document. HTML Validator is currently set to stop after 20 errors. 56. Message in line 284 at character 1102: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "IMG" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 57. Message in line 284 at character 2106: (Grouped->Good Style) [7] The "height" and "width" attributes should be used with the "IMG" element. Using these attributes generally result in faster and smoother (less jumpy) rendering. Using them is also considered to be good style. 58. Comment: (Accessibility->Accessibility Tips) This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options. 59. Comment: The ampersand '&' is an escape character in HTML. If you want to actually use the ampersand in your HTML document, then the character entity reference '&' should be used instead of the actual ampersand character. 60. Comment: Possibly misspelled words (16, 6 unique): froweey (1x), Swicth (1x), mwk (2x), VDS (3x), WowBB (3x), WowUltra (6x). NOTE: Validation terminated so not all words were checked. 61. Comment: You can change the maximum number of error messages to display before the validation is terminated. This option is in CSE HTML Validator's Validator Engine Options. 62. Comment: HTML 4.01 Transitional document detected. 63. Comment: (Grouped->Search Engine) [113] Random Search Engine Tip #8 - Using the "alt" attribute for images is not just good for accessibility, it's good for search engines too. Use the "alt" attribute to describe images but use relevent keywords and search terms in the description when appropriate, but don't overdo it by cramming in too many keywords. 64. Comment: (Grouped->Search Engine) [8] should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. 65. Comment: (Grouped->Search Engine) [8] should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu or from the Tag Inserter. 66. Comment: An ICRA RDF label was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. It is recommended that every page include an ICRA label. For more information, please visit http://www.icra.org/. 67. Comment: [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation. 68. Comment: CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation. 69. Comment: 26222 bytes; 18.2s@14.4Kbps, 9.1s@28.8, 5.2s@50, 4.1s@64, 2.0s@128, 0.7s@384, 0.5s@512, 0.3s@768, 0.2s@1.5Mbps, 0.0s@10Mbps. 70. Comment: 0.19s, 21 errors, 7 warnings, 29 messages, 13 validator comments, 337 lines, 252 tags (172 closed), 2 document comments, 11 entities, 753 programs run. Hope it helps. My experience is that it is only a minor issue. Best Markus
|
||||||||||||||
| |||||||||||||||
| |||||||||||||||
|
Jim Administrator
|
*Makes note to add the "go to bottom" button* Whad exactly did you validate? The index page? I actually took tables out in the stock theme.
|
||||||||||||||
| |||||||||||||||
| Current time is 04:52 am | |
| UltraBB Forums > UltraBB > Troubleshooting > Order of blocks in Ultra look | |
