Tres and I talked yesterday about the conditional templating part.  I  
don't think even *that* is immediately obvious, much less merging of  
class values, much less attribute removal.

We think we need a way to play with some of the ideas, without  
throwing the locked-down nature of the declarative side at it.  I  
think Tres and I will explore the idea of a middleware step just  
before/after Deliverance, where you do some things in Python.  Or  
perhaps within Deliverance, so we don't have to re-parse the HTML  
string into a tree.

--Paul

On Feb 14, 2008, at 10:11 AM, Wichert Akkerman wrote:

> Normally replacing the attribute is best. But I do want the ability  
> to merge CSS
> classes, so an option that merges words lists would be useful (ie  
> turn "one two"
> and "two three" into "one two three").
>
> I don't think it is useful to support merging of style attributes.  
> Anyone using
> those instead of proper CSS deserves the pain.
>
> I'm wondering if it would be useful to support removal of  
> attributes. I can see
> a use for doing things like removing js events (ie remove onchange  
> from an input
> element) but I don't think
> that is a high priority. This may already be possible with the  
> existing drop rule.
>
> __________________________________
> Repoze Bugs <bugs@bugs.repoze.org>
> <http://bugs.repoze.org/issue23>
> __________________________________
> _______________________________________________
> Repoze-dev mailing list
> Repoze-dev@lists.repoze.org
> http://lists.repoze.org/listinfo/repoze-dev