Terse mode only enabled after the doctype has been processed

[leider]

Rendering a tag with an attribute that does not have a value, like <div ui-view></div> works only if done from within one jade file but not via included mixin.

See pull request #1917

PR is only for documentation.

Question: Is this a bug, feature or "tragic" side effect?

[ForbesLindesay]

Thanks for reporting. This is true of any code that is "above" the doctype. Essentially the default doctype is something akin to xhtml, but it changes to the more modern html doctype when it sees doctype html. We should really be able to make this work regardless of where the doctype is specified.

[TimothyGu]

Deassigning this to 2.0.0. It's not of blocking significance.

[leider]

agree. Shall I leave the issue open?

[TimothyGu]

Yes please.

On Sun, Nov 1, 2015 at 1:33 AM Andreas Leidig [email protected]
wrote:

agree. Shall I leave the issue open?

—
Reply to this email directly or view it on GitHub
#1918 (comment).

[bartdorsey]

I just ran into this bug, and it manifested in a slightly different and unusual way. We had a mixin that appeared in a template AFTER a extends layout.pug. The layout file contains the doctype.html but somehow inside the mixin terse mode isn't enabled.

extends layout.pug

mixin option(value, text)
  option(value=value selected=(value === favoriteBeatle)) #{text}

block content
   +option('John', 'John')

I'm assuming this is because the extends happens after the mixin is parsed or something.

As a workaround for now, if you put the mixin inside of the block content it works fine, but I thought I would post this here as addition information related to this bug.

[bartdorsey]

Honestly at this point pug should just REMOVE the whole concept of terse mode and always render the attributes according to the HTML5 standard.

[ajimix]

I'm also facing this problem as it's now common in the HTML5 standard to have terse attributes but pug has this issue.
The issue was opened in 2015 and based on the lack of updates in Pug recently, it seems unlikely that this will ever be addressed.