Wed, 05 Feb 2014 15:50:36 +0100 [uilib] allow canvas tags in the html cleaner stable
Julien Cristau <julien.cristau@logilab.fr> [Wed, 05 Feb 2014 15:50:36 +0100] rev 9524
[uilib] allow canvas tags in the html cleaner Used by the iprogress cube. Closes #3524254.
Wed, 05 Feb 2014 16:34:21 +0100 [ajax] use a custom tag to handle dynamically loaded js stable
Julien Cristau <julien.cristau@logilab.fr> [Wed, 05 Feb 2014 16:34:21 +0100] rev 9523
[ajax] use a custom tag to handle dynamically loaded js Using <pre class="script"> makes it trivial for a malicious user to inject arbitrary javascript into a html or rest text element (because it looks innocent to the html sanitizer). Using a custom tag we can be sure that it actually comes from our code and not from untrusted user data. IE ignores custom tags, though, so we put it in its own namespace. https://extranet.logilab.fr/1530578
Mon, 03 Feb 2014 19:07:58 +0100 [dataimport] fix comment stable
Aurelien Campeas <aurelien.campeas@logilab.fr> [Mon, 03 Feb 2014 19:07:58 +0100] rev 9522
[dataimport] fix comment
Wed, 12 Feb 2014 18:15:32 +0100 [hooks/security, devtools/fill] silence yams 0.38.0 warnings stable
Aurelien Campeas <aurelien.campeas@logilab.fr> [Wed, 12 Feb 2014 18:15:32 +0100] rev 9521
[hooks/security, devtools/fill] silence yams 0.38.0 warnings
Mon, 03 Feb 2014 16:30:07 +0100 Drop 3.13 incomplete backward compat in edit controller.
Florent Cayré <florent.cayre@logilab.fr> [Mon, 03 Feb 2014 16:30:07 +0100] rev 9520
Drop 3.13 incomplete backward compat in edit controller. It is very old and broken (there is another non-backward-copmpatible usage of `_cw_entity_fields`), better to remove it instead of fixing. Closes #3515223.
Mon, 10 Feb 2014 16:06:16 +0100 [devtools] force locale to C for postgresql test clusters
Julien Cristau <julien.cristau@logilab.fr> [Mon, 10 Feb 2014 16:06:16 +0100] rev 9519
[devtools] force locale to C for postgresql test clusters Avoids initdb failure with e.g. iso8859-X locale and utf-8 encoding.
Fri, 20 Dec 2013 08:39:03 +0100 [rql2sql] remove special behaviour of symmetric relation vs DISTINCT
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 20 Dec 2013 08:39:03 +0100] rev 9518
[rql2sql] remove special behaviour of symmetric relation vs DISTINCT 0542a85fe667 replacing SQL OR by hooks for symmetric relations allows that. This involve a single test value change for a border case: when querying a symmetric relation without specifying the subject nor the object, you may get some duplicated result. IMO this is fine to let the user explicitly use DISTINCT or not and to remove the dedicated handling we had which didn't let any choice. Related to #3259713
Tue, 11 Feb 2014 11:03:01 +0100 Typo in comments and error messages
Dimitri Papadopoulos <dimitri.papadopoulos@cea.fr> [Tue, 11 Feb 2014 11:03:01 +0100] rev 9517
Typo in comments and error messages
Thu, 13 Feb 2014 15:11:07 +0100 Fix typo in a setup.py comment
Dimitri Papadopoulos <dimitri.papadopoulos@cea.fr> [Thu, 13 Feb 2014 15:11:07 +0100] rev 9516
Fix typo in a setup.py comment
Thu, 13 Feb 2014 15:09:30 +0100 [dataimport, migration] more fixes in the spirit of a6c32edabc8d:
Dimitri Papadopoulos <dimitri.papadopoulos@cea.fr> [Thu, 13 Feb 2014 15:09:30 +0100] rev 9515
[dataimport, migration] more fixes in the spirit of a6c32edabc8d: [entity, metadata] huuum, use resolvable url as cwuri... And fix existing ones. Closes #3390388
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip