AS> Ed -
AS> I find the use of JSON here very confusing and unnecessarily complex.
AS> Two simpler options that I would prefer:
AS> 1. Enhance f:attribute to allow pass-thru of data- attributes, eg:
AS> <f:attribute name="data-andy-rocks" value="false"/>
AS> Thinking the <f:attribute> handler would populate a map that hangs off
AS> of the component's attribute map. Renderers would be required to
AS> iterate over this map and blast out all of attributes.
AS> 2. Add a new f:dataAttribute tag, eg:
AS> If we prefer not to complicate <f:attribute>, we could do:
AS> <f:dataAttribute name="andy-rocks" value="false"/>
AS> With a similar implementation.
AS> Ideally either/both of these would support EL-binding, eg:
AS> <f:dataAttribute name="andy-rocks" value="#
>> If the view being rendered is not HTML5, the value of this attribute
>> must be ignored.
AS> I would lean towards passing these through regardless of the target
AS> markup language. Although data- attributes are not strictly valid
AS> pre-HTML5, simply dropping these might make life more difficult for an
AS> app developer who needs to target a range of browsers (including both
AS> HTML5 and pre-HTML5 browsers).