GitHub PushEvent at 2014-03-24 00:22:06
Repository: testng
Actor: themainfunction
Payload: {"shas":[["33ac8cbb811d1d0fe6562dc4f756606a53d3875c","0a3ba1af216659500dd8f41e29f3979f42452870@themainfunction.com","Fixed TOC anchor collisions in documentation-main.html\n\nThe table of contents' section links are generated from\nanchors of class 'section. There were two collisions of\nthe anchor names, where two sections shared the same\nanchor name:\n\nSections 'Test methods' and 'Test groups' both used the\n\tanchor name 'test-groups'\nSections 'Parallel suites' and 'Parallel tests, methods,\n\tand groups' used the anchor name 'parallel-tests'\n\nNow, these are fixed, with anchor names that match the\nsection names, and the TOC links work properly.\n\nThe anchors for the table of contents are specified by the\nname attribute.","The Main Function (Bryan)",true],["a9adb55fc1eed2283ec20975b13ee2fc104d1281","0a3ba1af216659500dd8f41e29f3979f42452870@themainfunction.com","Fixed section heading tags (<h3>, <h4>, <h5>) so they are consistent\n\nSections and subsection headers were inconsistent in their usage\nof html heading tags.\n\nThe majority of section headings use the following tags based on\ntheir indent attribute:\n\nindent=\".\" or blank =>  <h3>\nindent=\"..\"         =>  <h4>\nindent=\"...\"        =>  <h5>\n\nHowever, some of the \"...\" level tags used <p><em></em></p> or even\n<h3> some times. There were inconsistencies like this in a few places.\n\nNow, all of the section headings conform to the above scheme.","The Main Function (Bryan)",true],["fb46792d8166299d5fdb2054eb9ac266e58e932c","0a3ba1af216659500dd8f41e29f3979f42452870@themainfunction.com","Standardized section heading HTML format for easier reading/maintenance.\n\nThe HTML for the section headings varied between headings. Sometimes\nthe <h> tags were on surrounding lines, sometimes they wrapped the\ncontent on a single line, and sometimes they were at the end of the\nprevious line of content. This made for difficult reading; it also made\nchanges difficult.\n\nNow, all section heading <h> tags wrap the content on a single line,\nin the following format:\n\n<hx><a ...>content</a></hx>\n\nso that they are easy to work with.\n\nNOTE: I'm aware that this may not be compliant with some style guides,\nand also that everybody has different preferences. I'm not trying to\nenforce my particular preference over anyone else's; I picked this\nformat simply because A) section heading lines are generally short\nenough to fit in screen-width even with <h> tags, and B) many of the\nsection headings were this way to begin with.","The Main Function (Bryan)",true],["6d500ad200be1406b4db6ffc75db3975bac1f1b2","0a3ba1af216659500dd8f41e29f3979f42452870@themainfunction.com","Misc file formatting for documentation-main.html\n\nNone of the actual content has changed with this commit, so the\nrendered webpage should be identical. However, the file itself\nwas hard to read and hard to edit, due to things like lists being\nsmooshed together into one line, or the closing tag of one paragraph\nsitting at the beginning of the following paragraph, etc. This also\nmakes it difficult to look at the html and understand structure, for\nexample.\n\nThese are not in any way comprehensive, nor are the focused on\nDTD compliance, etc. The main purpose is bringing the file into a\nmore workable state (though in some places, fixes are made, e.g.\nclosing tags added where they were missing, etc).\n\nMainly the changes are:\n\n*Fixed all lists. Many of them had unclosed <li> tags; some of them\nwere jumbled into one long run-on line that even included preceding\nor following <p> tags. Most of them were simply difficult to read.\nThe lists are now in the format:\n\n<ul>\n  <li>\n    content.\n  </li>\n</ul>\n\nsimply so that it's easy to see where the list starts and ends, if\nthe list items have both opening and closing tags, etc.\n\n*A few very long lines (hundreds of columns) are split into shorter\nlines.\n\n*Content wrapped in <p> tags that had been smooshed together with\nother paragraphs or lists now has its own line.\n\nNOTE: Just to reiterate, I'm not trying to make things standard\ncompliant with this, or to conform to style guidelines, or to\nforce anyone to favor one style over another. I'm simply making\nthe documentation easier to work with.","The Main Function (Bryan)",true]],"size":4,"ref":"refs/heads/master","head":"6d500ad200be1406b4db6ffc75db3975bac1f1b2"}