[ZCM] [ZC] 2223/ 3 Reject "tal:attribute test forward porting"

Issue #2223 Update (Reject) "tal:attribute test forward porting"
 Status Rejected, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2223

==============================================================
= Reject - Entry #3 by philikon on Jan 8, 2007 7:34 am

 Status: Accepted => Rejected

The test that was added tries the following::

  <p tal:attributes="disabled python:True and default or 'disabled'"></p>
  <p tal:attributes="disabled python:False and default or 'disabled'"></p>

and expects the following output::

  <p></p>
  <p disabled="disabled"></p>

This test is a bit bogus as 'disabled' is one of those HTML "boolean" attributes (like 'selected' in '<option selected="selected">'). The test should read:

  <p tal:attributes="disabled python:True"></p>
  <p tal:attributes="disabled python:False"></p>

(of course, True and False would be actual expressions that return True or False). The TAL interpreter figures out the rest.

So, whichever backward compatibility problem Zope 2.10 introduced, it's really a problem of improper usage of the 'disabled' attribute and should be fixed in whichever software (Plone 3?) that makes use of this feature.

Note that everything works as expected for "normal", non-boolean attributes.

I'm going to back out the test again.
________________________________________
= Assign - Entry #2 by philikon on Oct 28, 2006 2:42 pm

 Status: Pending => Accepted

 Supporters added: philikon

 
________________________________________
= Request - Entry #1 by wichert on Oct 26, 2006 1:31 pm

I added a unittest for tal:attribute conditional handling to the 2.9 branch in changeset 70918. This needs to be forward ported to 2.10 and trunk, which currently fail the test.
==============================================================