News for DOMBuilder

2.1.6 / 2012-06-29

  • Updated to isomorph 0.2.

2.1.5 / 2012-06-27

  • Fixed bug with not recognising tag names containing numbers.

2.1.4 / 2012-06-27

  • Added support for jade-style definition of tags with id and classes to
  • Fixed error creating tags without attributes using with DOM mode.

2.1.3 / 2012-05-31

  • Periods are now allowed on the RHS of ForNode expressions, so it’s possible to look up items to be iterated over from another template context variable.

2.1.2 / 2012-05-29

  • Now using Concur to define TemplateNode so it can more easily be inherited from.

2.1.1 / 2012-02-01

  • Fixed browser build - IE7/8 object.hasOwn incompatibility fixed in isomorph.

2.1.0 / 2012-01-27

  • Added DOMBuilder.template, starting implementation of Template mode - the API should not be considered stable until Version 2.2.

2.0.1 / 2011-08-06

  • Fixed nodeName checks in fallback attribute setting code.
  • Fixed error setting button/@value in IE6/7 when not using jQuery.

2.0.0 / 2011-07-17

  • Output modes are now pluggable, using DOMBuilder.addMode.
  • Output mode specific element functions are now available under DOMBuilder.dom and DOMBuilder.html.
  • HTML Mode no longer has any dependency on DOM Mode.
  • Updated attribute-setting code based on jQuery 1.6.2.
  • Nested Array representations of HTML can now be used to generate output with an output mode, using
  • Nested Array structures can be built using element functions under DOMBuilder.array.
  • Added support for new tags defined in HTML 5.
  • You can now specify a mode for DOMBuilder.apply, which will also apply any additional API for the specified mode, if available.

Backwards-incompatible changes:

  • When calling, the default attributes argument is now required - flexible arguments are now handled by the map functions exposed on element creation functions.
  • now passes a loop status object to the given mapping function instead of an index.
  • The context argument object to DOMBuilder.apply is now required.
  • DOMBuilder.apply no longer adds an NBSP property.
  • HTML mode mock DOM objects were renamed to MockElement and MockFragment.
  • HTML mode no longer supports XHTML-style closing slashes for empty elements.
  • markSafe and isSafe moved to DOMBuilder.html.markSafe and DOMBuilder.html.isSafe, respectively.

1.4.4 / 2011-05-19

  • Additional arguments can now be passed in to withMode to be passed into the function which will be called.

1.4.3 / 2011-04-26

  • Fixed defect doing child checks on null and undefined children.

1.4.2 / 2011-04-12

  • Added support for using the innerHTML attribute to specify an element’s entire contents consistently in DOM and HTML modes.

1.4.1 / 2011-03-04

  • Fixed HTML mode bug: event registration now works for nested elements.
  • DOMBuilder can now be used as a Node.js module, defaulting to HTML mode.
  • Fixed bug: SafeString is no longer used as an attributes object if passed as the first argument to an element creation function.

1.4.0 / 2011-02-13

  • Fixed HTML escaping bugs: attribute names and unknown tag names are now escaped.
  • A new insertWithEvents method on DOMBuilder.HTMLElement attempts to use innerHTML in a cross-browser friendly fashion. It’s safe to use this method on elements for which innerHTML is readonly, as it drops back to creating DOM Elements in a new element and moving them. If jQuery is available, its more comprehensive html function is used.
  • Fixed issue #1 - HTML mode now supports registering event listeners, specified in the same way as DOM mode, after HTML has been inserted with innerHTML. If necessary, id attributes will be generated in order to target elements which need event listeners.
  • Fixed issue #3 - jQuery is now optional, but will be made use of if present.

1.3.0 / 2011-02-04

  • Tag names passed into DOMBuilder.HTMLElement are now lower-cased.
  • Added DOMBuilder.elementFunctions to hold element creation functions instead of creating them every time DOMBuilder.apply() is called. This also allows for the possibility of using a with statement for convenience (not that you should!) instead of adding element creation functions to the global scope.
  • Added to create contents from a list of items using a mapping function and wrap them in a single fragment as siblings, negating the need for redundant wrapper elements.
  • Fixed (Google Code) issue #5 - added HTMLFragment.toString().
  • Fixed (Google Code) issue #3 - we now append “nodey” contents (anything with a truthy nodeType) directly and coerce everything else to String when appending child nodes, rather than checking for types which should be coerced to String and appending everything else directly.
  • Bit the bullet and switched to using jQuery for element creation and more. DOMBuilder now depends on jQuery >= 1.4.
  • Fixed (Google Code) issue #2 - nested Array objects in child arguments to DOMBuilder.createElement() and DOMBuilder.fragment() are now flattened.
  • Extracted HTMLNode base class to contain common logic from HTMLElement and HTMLFragment.
  • Renamed Tag to HTMLElement.
  • DOMBuilder.fragment now works in HTML mode - DOMBuilder.HTMLFragment objects lightly mimic the DOM DocumentFragment API.
  • Added to create elements based on a list, with an optional mapping function to control if and how resulting elements are created.
  • Added DOMBuilder.fragment(), a utility method for creating and populating DocumentFragment objects.

1.2.0 / 2011-01-21

  • Created Sphinx docs.
  • Tag objects created when in HTML mode now remember which mode was active when they were created, as they may not be coerced until a later time, when the mode may have changed.
  • Added DOMBuilder.withMode() to switch to HTML mode for the scope of a function call.
  • Fixed short circuiting in element creation functions and decreased the number of checks required to determine which of the 4 supported argument combinations the user passed in.
  • Attributes are now lowercased when generating HTML.
  • DOMBuilder.isSafe() and DOMBuilder.markSafe() added as the public API for managing escaping of strings when generating HTML.
  • Added support for using the DOMBuilder API to generate HTML/XHTML output instead of DOM elements. This is an experimental change for using the same codebase to generate HTML on the backend and DOM elements on the frontend, as is currently being implemented in

1.1.0 / 2008-10-10

  • An NBSP property is now also added to the context object by DOMBuilder.apply(), for convenience.
  • Boolean attributes are now only set if they’re true. Added items to the demo page to demonstrate that you can now create an explicitly unchecked checkbox and an explicitly non-multiple select.
  • Added more IE workarounds for:
    • Creating multiple selects
    • Creating pre-selected radio and checkbox inputs

1.0.0 / 2008-06-01

  • Added support for passing children to element creation function as an Array.
  • Added more robust support for registering event handlers, including cross-browser event handling utility methods and context correction for IE when the event handler is fired.
  • IE detection is now performed once and once only, using conditional compilation rather than user-agent String inspection.