The capitalisation of headerContent when creating a FormOverlay is inconsistent and confusing

[Graham Binns]

When creating a FormOverlay you can pass a headerContent variable, which contains the header for the FormOverlay. Every other variable that gets passed when creating a FormOverlay is underscore_delimited, whereas headerContent is camelCapped. This inconsistency is confusing and could lead to unnecessary rage.

[Curtis Hovey (sinzui)]

headerContent comes from YUI's WidgetStdMod. To support Launchpad's style, Lp's overlay needs a header_content in ATTRS that also sets headerContent. We may also need to redefine headerContent because anything from YUI's code that sets headerContent also needs to update Lp's header_content.

I doubt we want to do this.

[Richard Harding (rharding)]

I'm with Curtis. This is a YUI API standard we're working against. We could attempt to wrap it, but the corner cases of keeping values in sync would be more of a pain than it would solve in my opinion.

I think the better solution would be to get YUIDoc running and providing developers with better API documentation that would help make this more obvious.