« Changelog History


Fortitude v0.0.2 Release Notes

Release Date: 2014-06-21 // almost 10 years ago
    • Void tags (those that can't take content, ever, like <hr> or <br>) are now never closed in HTML4 doctypes (i.e., just output as plain <hr>, with no close tag), since using self-closing syntax (<hr/>) is broken and an end tag (</hr>) is illegal according to the W3C Validator. In XHTML doctypes, they are always closed using self-closing syntax (<hr/>) since they have to be closed somehow and that's a good way to indicate that they are void (can't ever take content). In HTML5, they are left unclosed by default (since HTML5 knows they're void and isn't expecting an end tag for them, ever), but you can use close_void_tags true to add self-closing syntax for them (<br/>) if you want, since that is now allowed in HTML5. See this article for even more discussion.
    • Empty tags (those that can take content, but just happen not to) are now always closed using a separate tag (e.g., <p></p>), since it is not legal or correct to use self-closing syntax (<p/>) here in HTML doctypes (HTML4 or HTML5), and it is perfectly legal in XHTML doctypes to use a separate closing tag — and, in a way, nice, since it lets you visually differentiate between void tags and normal tags that just happen to be empty.
    • 🔨 Very significant internal refactoring of code to make development easier, and new developers' lives easier.
    • 🛠 Fixed support for Tilt < 2.x; earlier Tilt versions expect to be able to instantiate a template class with an empty string and have it not raise an exception, as a way of testing whether an engine works. (Empty strings are not valid Fortitude templates, since we expect to see a class declaration in there.) Now we trap that case explicitly to do nothing, which allows Tilt 1.4.x to work.