Take advantage of existing DOM when using a single yield

[wintercounter]

Help us to manage our issues by answering the following:

1. Describe your issue:

Currently we're using riot in a PHP based environment. So we're having our templates coming from PHP. We introduced a simple way to allow riot expressions in those templates. It's pretty simple:

Markup from PHP

<my-tag>
    <div class="{cls}">Content</div>
</my-tag>

Tag

<my-tag>
    <yield></yield>
    this.cls = 'my-cls'
</my-tag>

This works fine, the only issue is FOUC which could be easily prevented if riot would take the advantage of the existing DOM when only using a single yield in the tag. The DOM structure isn't changing there anyway. This would have performance benefits also. (I know this won't ever make it into riot, but worth a shot).

2. How would you tag this issue?

• Question
• Bug
• Discussion
• Feature request
• Tip
• Enhancement
• Performance

[wintercounter]

Or maybe it can work by leaving out the yield tag (no markup). It's like just simply attaching riot's functionality to a natural DOM element, sound pretty clear.

[GianlucaGuarini]

In the next riot release for the tags declared with no template riot will use just their inline html as template http://plnkr.co/edit/DYp1iSiqpeM5XogBmB1n?p=preview

[wintercounter]

Wow! I didn't expect this, you guys are great!

[CodeKris]

Awesome!
There's a syntax error in the docs:

riot.tag.('tag-name', false, function(opts) { // Extra dot after 'tag'

Kris