Denis Laxalde <denis.laxalde@logilab.fr> [Wed, 28 Jan 2015 17:36:13 +0100] rev 10168
[doc] Fix class name for ComputedRelation; fix code block about computed attributes
Rémi Cardona <remi.cardona@logilab.fr> [Thu, 29 Jan 2015 16:40:08 +0100] rev 10167
[web] Allow propagating 'klass' parameter on tree views recursively
Closes #4881302
Rémi Cardona <remi.cardona@logilab.fr> [Wed, 28 Jan 2015 11:59:06 +0100] rev 10166
[utils] Fix define_var in ajax context (closes #4881301)
Use namespaced <cubicweb:script> instead of just <script>
Rémi Cardona <remi.cardona@logilab.fr> [Wed, 28 Jan 2015 11:53:20 +0100] rev 10165
[web/data] Never hide JS errors in our Deferred implementation
Modern browsers have good debugging tools, let exceptions go all the way
up. This only affects exceptions raised in the js code, if there's an
issue on the server/python side, they'll keep going through our error
callbacks.
Closes #4881300
Rémi Cardona <remi.cardona@logilab.fr> [Wed, 28 Jan 2015 11:51:16 +0100] rev 10164
[web/data] Fix userCallbackThenUpdateUI to completely replace old DOM elements
Without the 'swap' parameter, userCallbackThenUpdateUI() would replace
the _children_ of the component with a new version of the componenent,
thus creating nested divs/spans/buttons/etc.
Closes #4881299
Rémi Cardona <remi.cardona@logilab.fr> [Fri, 30 Jan 2015 15:53:32 +0100] rev 10163
[web/views] Stop mishandling the fieldset name in the default form renderer
While not really documented, it is generally assumed that:
* the fieldset is a user-visible string (much like a title),
* it will be translated by whichever piece of code uses it.
So:
* fix AutomaticEntityForm to generate untranslated fieldset names,
* fix FormRenderer to properly translate the fieldset name before
rendering it,
* stop using the field set (which may contain whitespace) as a CSS class
name (the feature was unusable, so just drop it),
* properly handle the colon as part of the translated fieldset name
Closes #4881298