ANATOMY OF A TABLE: REMOVED BY FB

ANATOMY OF A TABLE: REMOVED BY FB

8. div.c7 {text-align: center} 9. table.c6 {background-color: #FFFFFF} 10. td.c5 {background-color: #0000FF; text-align: center} 11. div.c4 {font-size: 150%} 12. span.c3 {background-color: rgb(255, 255, 255);} 13. td.c2 {background-color: #0000FF} 14. div.c1 {text-align: left;} 15. 448. div.c9 {background-color: rgb(0, 0, 0); text-align: center;} 449. table.c8 {margin-left: auto; margin-right: auto; text-align: left;} 450. td.c7 {background-color: rgb(255, 0, 0);} 451. div.c6 {margin-left: 80px;} 452. table.c5 {background-color: #FFFFFF} 453. td.c4 {text-align: center;} 454. h1.c3 {font-size: 150%} 455. td.c2 {background-color: #FF0000} 456. br.c1 {background-color: rgb(0, 0, 0);} 457. br.c18 {background-co… * Line 298, column 65: document type does not allow element} div.c17 {text-align: center;} span.c16 {font-size: 70%} blockquote.c15 {font-size: 70%} h1.c14 {font-size: 150%} span.c13 {color: #FF0000; font-size: 150%} div.c12 {font-size: 150%} blockquote.c11 {font-size: 150%} div.c10 {background-color: rgb(0, 0… * Line 327, column 118: document type does not allow element} div.c9 {background-color: rgb(0, 0, 0); text-align: center;} table.c8 {margin-left: auto; margin-right: auto; text-align: left;} td.c7 {background-color: rgb(255, 0, 0);} div.c6 {margin-left: 80px;} table.c5 {background-color: #FFFFFF} td.c4 {text-align: center;} span.c3 {font-size: 150%} td.c2 {background-color: #FF0000} br.c1 {background-color: rgb(0, 0, 0);} -->

Below is the source input I used for this validation: 1. 2. 3. 4. 5. 6. 7. 16. 17. 18.

19. 1.
20.

2. 21. 22. 3div style=bg-c

3br
23. 3divclass=c4 24.

3br
25. 26. 4. 27. 4table class c3 zero border28. 29. 5tbody 30. 31. 32. 33. 6trValidation Output: 84 Errors 1. Warning unclosed start-tag requires SHORTTAG YES ✉ The construct is valid in HTML (it is an example of the rather obscure "Shorttags" feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers. * Line 35, column 31: unclosed start-tag requires SHORTTAG YES

9

aragraph

), or * forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or * using XHTML-style self-closing tags (such as ) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML. * Line 29, column 1: character data is not allowed here 5tbody * Line 33, column 1: character data is not allowed here 6tr

34. 7td class c2 align center91. 92. 18a. 93. 185. 187. 188. 189.

8. div class c1 35. 9 81. 82. 83. 15a. close a 84. 85. 86. 16a. close /div 87. 88. 89. 90. 17a.	94. 95. 96. 97. 19a. 98. 99. 100. 101. 102. 103. 20a. 104. 105. 106. 107. 108. 109. 110. 111. 112. 113. 114. 115. 116. 117. 168. 169. 170. 171. 172. 173. 174. 175. 176. 177. 118. 119. 120. 121. 122. 123. 124. 125. 126. 127. 128. 129. 130. 131. 135. 136. 137. 138. 139. 140. Clash-a-thon 141. 142. 143. 144. 145. 146. 147. 148. 149. 150. 151. 152. 153. 154. 155. 156. 157. 158. 159. 160. 161. 162. 163. 164. 165. 166. 167. 178. 179. 180. 181. 182. 183. 23. 184. 24.	186. 26.

190. 30.
191. 31.

192. 32.
193. 33.

194. 34.
195. 196. 197. 198. 199. ↑ 200. 201. 202. 203. 204. 205. 206. 207. 208. 209. 210. 211. 212. 213. 214. 235. 236. 237. 238. 239. 240. 241. 242. 243. 244. 245. 246. 247. 248. 249. 250. 251. 252. 253. 254. linked title of Page url this writes in plain text and inherits the h1 from above (or below) don't see an open one above?? 255. 256. 257. 259. 260. Clash-a-thon (CLOSE SPAN) 261. 262. 263. END OF CLOSE SPAN 264. 265. BEGINNING OF CLOSE A/ 266. 267. END OF CLOSE A/ 268. 269. WHY AM I INHERITING THE SUBSEQUENT H1 WHICH IS FOR 'CLASH A THON PLAIN BUT BOLD'?

↑

270.

↑

271. 272. 273. 274. 275. 276. 277.

Clash-a-thon

END CLASH ATHON H1 278. 279. CLOSE BODY 280. 281. 282. CLOSE HTML 283. 284. 285. 286. 287. 288. 289. 290. 291. 292. 293. 294.

W3C Markup Validation
295.

296. 297. 298.

299. 300.

301. 302.303. 304. 305. 306. 307. 308. 313. 314. 9. Error character X not allowed in attribute specification list ✉ * Line 257, column 77: character "[" not allowed in attribute specification list …/video-Clash-a-thon/167248373319135" [[[end of link as long as you don't writ… 10. Error no document type declaration; implying X ✉ The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid. * Line 2, column 1: no document type declaration; implying "" 11. Error X is not a member of a group specified for any attribute ✉ * Line 35, column 27: "OPEN" is not a member of a group specified for any attribute

9

9 * Line 80, column 13: "HEIGHT" is not a member of a group specified for any attribute 14a. height 95 height="95"> * Line 80, column 13: "95" is not a member of a group specified for any attribute 14a. height 95 height="95"> 12. Error document type does not allow element X here; assuming missing Y start-tag ✉ * Line 249, column 7: document type does not allow element "TBODY" here; assuming missing "TABLE" start-tag

13. Error document type does not allow element X here; missing one of Y start-tag ✉ The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as "

" or "

") inside an inline element (such as "", "", or ""). * Line 269, column 85: document type does not allow element "H6" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag …ERITING THE SUBSEQUENT H1 WHICH IS FOR 'CLASH A THON PLAIN BUT BOLD'?

↑

* Line 270, column 4: document type does not allow element "H6" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

↑

* Line 277, column 4: document type does not allow element "H1" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

Clash-a-thon

END CLASH ATHON H1 * Line 327, column 52: document type does not allow element "BR" here; missing one of "TH", "TD" start-tag …tyle="background-color: rgb(0, 0, 0);">

* Line 497, column 103: document type does not allow element "H6" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag …is document, automatically generated from the heading tags (

through

.) 14. Warning NET-enabling start-tag requires SHORTTAG YES ✉ The sequence can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag '). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. * Line 35, column 137: NET-enabling start-tag requires SHORTTAG YES …itle 10 title=httpprofile.ak.fbcdn.net/hprofile-ak-snc4/161998_167248373319135… ↑ Top Source Listing BEGINNING OF THIRD STYLE CSS SECTION WHICH IS ALSO DISPLAYING AS PLAIN TEXT wHY? dOESN'T sPACE HOWEVER.

1.

2. 3div style=bg-c

3br
3divclass=c4

3br
4. 4table class c3 zero border5tbody 6tr7td class c2 align center18a.

8. div class c1 9 15a. close a 16a. close /div 17a.

19a. 20a. Clash-a-thon 23. 24.

26.

25

linked title of Page url this writes in plain text and inherits the h1 from above (or below) don't see an open one above??

Clash-a-thon (CLOSE SPAN) END OF CLOSE SPAN BEGINNING OF CLOSE A/

END OF CLOSE A/

WHY AM I INHERITING THE SUBSEQUENT H1 WHICH IS FOR 'CLASH A THON PLAIN BUT BOLD'?

Clash-a-thonWHY AM I INHERITING THE SUBSEQUENT H1 WHICH IS FOR 'CLASH A THON PLAIN BUT BOLD'?

END CLASH ATHON H1 CLOSE BODY CLOSE HTML

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXX

Error found while checking this document as HTML 4.01 Transitional! Result: 1 Error, 4 warning(s) Source:

Clash-a-thon 1. 2 3 4. 5. 6. 7. 10. 25. 27. 28. 29. 8. 9. 11. 12. 13. 14. 15. 20. 21. 22. 16. 17. Clash-a-thon 18. 19. 23. 24. 26. 30. 31. 32. 33. 34. ↑ Clash-a-thon

XXXXXXXXXXXXXXXXXXXXXX

This service runs the W3C Markup Validator, v1.1. Copyright ©

XXXXXXXXXXXXXXXXXXXXXXXXX

309. 310. 311. 312.

315. 316. 317. 318. 319. 320. 321. 322. 323. 324. 325. Error found while checking this document as HTML 4.01 Transitional! 326. Result: 1 Error, 4 warning(s) 327. Source: Clash-a-thon 328. Modified: 329. Server: 330. Size: 331. Content-Type: 332. Encoding: utf-8 333. Doctype: HTML 4.01 Transitional 334. Root Element: br 335. HP LogoThe W3C validators are hosted on server technology donated by HP, and supported by community donations. 336. Donate and help us build better tools for a better web. 337. Options 338. Show Source Show Outline List Messages Sequentially Group Error Messages by Type 339. Validate error pages Verbose Output Clean up Markup with HTML Tidy 340. 341. Help on the options is available. 342. Notes and Potential Issues 343. 344. The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document. 345. 346. 1. 347. 348. Warning Unable to Determine Parse Mode! 349. 350. The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because: 351. * in Direct Input mode, no MIME Media Type is served to the validator 352. * No known Document Type could be detected 353. * No XML declaration (e.g ) could be found at the beginning of the document. 354. * No XML namespace (e.g ) could be found at the root of the document. 355. 356. As a default, the validator is falling back to SGML mode. 357. 2. 358. 359. Warning No DOCTYPE found, and unknown root element. Aborting validation. 360. 361. The DOCTYPE Declaration was not recognized or is missing. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax, or that your document is not using a DOCTYPE Declaration. 362. 363. Without a DOCTYPE Declaration it is not possible to check the validity of your document. Since the document does not start with the root element, automatic fallback to an HTML document type was not performed, and most of the validation process was aborted: only basic markup syntax was checked. 364. 365. Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type. 366. 3. 367. 368. Info No Character encoding declared at document level 369. 370. No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc. 371. 372. See this tutorial on character encoding for techniques and explanations. 373. 4. 374. 375. Info Using Direct Input mode: UTF-8 character encoding assumed 376. 377. Unlike the "by URI" and "by File Upload" modes, the "Direct Input" mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified. 378. 379. If you notice a discrepancy in detected character encoding between the "Direct Input" mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document. 380. 381. ↑ Top 382. Validation Output: 1 Error 383. 384. 1. Error no document type declaration; will parse without validation 385. 386. ✉ 387. 388. The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax. 389. 390. Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type. 391. * Line 1, column 1: no document type declaration; will parse without validation 392. 393. 394. 395. ↑ Top 396. Source Listing 397. 398. Below is the source input I used for this validation: 399. * Line 34, column 1: character data is not allowed here 7td class c2 align center* Line 405, column 4: character data is not allowed here 6. * Line 406, column 4: character data is not allowed here 7. * Line 413, column 3: character data is not allowed here 14. * Line 414, column 3: character data is not allowed here 15. * Line 420, column 3: character data is not allowed here 21. * Line 421, column 3: character data is not allowed here 22. ) could be found at the root of the docu… * Line 363, column 151: character data is not allowed here …t does not start with the root element, automatic fallback to an HTML d… * Line 395, column 1: character data is not allowed here ↑ Top 400. 1. 401. 2. 402. 3. 403. 4. 404. 5. 405. 6. 406. 7. 409. 10. 424. 25. 426. 27. 427. 28. 428. 29. 407. 8. 408. 9. 410. 11. 411. 12. 412. 13. 413. 14. 414. 15. 419. 20. 420. 21. 421. 22. 415. 16. 416. 17. Clash-a-thon 417. 18. 418. 19. 422. 23. 423. 24. 425. 26. 429. 30. 430. 31. 431. 32. 432. 33. 433. 34. 434. 435. ↑ Top 436. Cleaned-up Source Listing with "Tidy" 437. 438. Below is the cleaned up markup for your document, as processed through HTML Tidy. 439. 440. Tidy is a third-party software not developed at W3C, and its output is provided without any guarantee. 441. 442. 443. 444. 445. 446. 447. 458. 459. 460. 461. 462. 463. 464. 465. 466. 469. 484. 485. 486. 487. 467. 468. 470. 471. 472. 473. 474. 479. 480. 481. 475. 476. Clash-a-thon 477. 478. 482. 483. 488. 489. 490. 491. 492. 493. 494. ↑ Top 495. Document Outline 496. 497. Below is an outline for this document, automatically generated from the heading tags ( through .) 498. 499. [H1] Clash-a-thon 500. 501. If this does not look like a real outline, it is likely that the heading tags are not being used properly. (Headings should reflect the logical structure of the document; they should not be used simply to add emphasis, or to change the font size.) 502. 503. If you want to examine the semantic structure of your documents, beyond the outline, try the Semantic data extractor. 504. 505. ↑ Top 506. 507. * Home | 508. * About... | 509. * News | 510. * Docs | 511. * Help & FAQ | 512. * Feedback | 513. * Contribute | 514. 515. W3COpen-Source 516. 517. I heart Validator logo 518. 519. This service runs the W3C Markup Validator, v1.1. 520. 521. Copyright © 1994-2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements. * Line 401, column 4: character data is not allowed here 2. * Line 404, column 4: character data is not allowed here 5. * Line 409, column 3: character data is not allowed here 10. * Line 412, column 3: character data is not allowed here 13. * Line 419, column 3: character data is not allowed here 20. * Line 424, column 3: character data is not allowed here 25. * Line 427, column 3: character data is not allowed here 28. * Line 428, column 3: character data is not allowed here 29. * Line 426, column 3: character data is not allowed here 27. * Line 433, column 3: character data is not allowed here 34. * Line 435, column 1: character data is not allowed here ↑ Top * Line 494, column 1: character data is not allowed here ↑ Top 3. Error X not finished but document ended ✉ * Line 521, column 241: "HTML" not finished but document ended …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: "HTML" not finished but document ended …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: "TR" not finished but document ended …with this site are in accordance with our public and Member privacy statements. 4. Error document type does not allow element X here ✉ 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 35, column 137: document type does not allow element "A" here …itle 10 title=httpprofile.ak.fbcdn.net/hprofile-ak-snc4/161998_167248373319135… * Line 251, column 3: document type does not allow element "B" here * Line 294, column 12: document type does not allow element "BLOCKQUOTE" here W3C Markup Validation * Line 354, column 91: document type does not allow element "HTML" here …//www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the doc… * Line 363, column 149: document type does not allow element "HTML" here …ent does not start with the root element, automatic fallback to an HTML… * Line 393, column 56: document type does not allow element "BR" here * Line 400, column 50: document type does not allow element "BR" here 1. * Line 401, column 71: document type does not allow element "DIV" here 2. * Line 433, column 10: document type does not allow element "BR" here 34. * Line 442, column 6: document type does not allow element "HTML" here * Line 497, column 90: document type does not allow element "H1" here …is document, automatically generated from the heading tags ( through .) 5. Error end tag for X omitted, but its declaration does not permit this ✉ * You forgot to close a tag, or * you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed. The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag. * Line 281, column 7: end tag for "B" omitted, but its declaration does not permit this * Line 281, column 7: end tag for "TABLE" omitted, but its declaration does not permit this * Line 521, column 241: end tag for "H6" omitted, but its declaration does not permit this …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: end tag for "H1" omitted, but its declaration does not permit this …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: end tag for "TABLE" omitted, but its declaration does not permit this …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: end tag for "DIV" omitted, but its declaration does not permit this …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: end tag for "TABLE" omitted, but its declaration does not permit this …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: end tag for "DIV" omitted, but its declaration does not permit this …with this site are in accordance with our public and Member privacy statements. * Line 521, column 241: end tag for "DIV" omitted, but its declaration does not permit this …with this site are in accordance with our public and Member privacy statements. 6. Error there is no attribute X ✉ 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 element to incorporate flash media in a Web page, see the FAQ item on valid flash. * Line 104, column 61: there is no attribute "BORDERCOLOR" …lor="#ffffff" border="25" bordercolor="#000000" cellpadding="20" cellspacing="… * Line 104, column 123: there is no attribute "HEIGHT" …ordercolor="#000000" cellpadding="20" cellspacing="0" width="373" height="373"> * Line 354, column 47: there is no attribute "XMLNS" … * No XML namespace (e.g ) could be found at the root of the… 7. Error X not finished but containing element ended ✉ * Line 281, column 7: "TBODY" not finished but containing element ended 8. Error end tag for element X which is not open ✉ 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 241, column 6: end tag for element "DIV" which is not open * Line 243, column 5: end tag for element "TD" which is not open

Weirdopedia says: "Weird" http://weirdopedia.posterous.com/anatomy-of-a-table-removed-by-fb ANATOMY OF A TABLE: REMOVED BY FB 8. div.c7 {text-align: center} 9. table.c6 {background-color: #FFFFFF} 10. td.c5 {background-color: #0000FF; text-align: center} 11. div.c4 {font-size: 150%} 12. span.c3 {background-color: rgb(255, 255, 255);} 13. td.c2 {background-color: #0000FF} ...