The automatically generated spans around template calls easily create invalid html, e.g. by adding spans directly inside table elements. Also, library templates that replace built-ins currently all need the no-span modifier (unnecessary boilerplate code).

Submitted by Danny Groenewegen on 24 November 2010 at 11:37

On 24 November 2010 at 12:41 Danny Groenewegen commented:

To ease the migration for applications that actually use these spans (as hooks for CSS), we can add a span modifier for templates to include the previously automatic span.

On 24 November 2010 at 16:00 Danny Groenewegen closed this issue.

Log in to post comments