Fix #1228 - tagName can be provided as a function.

[braddunbar]

No description provided.

[jashkenas]

Why would we do this just for tagName, and not className and the rest?

[braddunbar]

className and attributes can already be provided as a function I believe (although only by virtue of jQuery, which doesn't use the view as context). Are there any others I'm missing (maybe id)? I suppose it would be nice to get the correct context with them as well. Perhaps we're overreaching here?

[jashkenas]

Out of curiosity, did you actually need this for your app ... or did it just seem like a good idea?

[braddunbar]

This request was submitted as a result of #1228. However, I have needed this before. What I did instead is to pass in the tag name before constructing the view, which is not great for encapsulation, or do the configuration in the constructor, which is less clear IMO.

As a contrived example:

var View = Backbone.View.extend({...});
...
if (options.p) options.tagName = 'p';
new View(options);

as opposed to

var View = Backbone.View.extend({
  tagName: function() {
    return this.options.p ? 'p' : 'div';
  },
  ...
});
...
new View(options);

[randallb]

I do need this for my app. I'm dynamically constructing "layers" (think photoshop) which can be different types. The example above here is precisely correct.