Message7247
Hmm this seems to work as well:
<tal:block tal:define="wins
python:utils.set_form_wins(request.client,False)"
tal:condition="context/id"
tal:replace="structure context/history" />
since tal:define runs before any other tal attributes. This
eliminates an additional span.
However with the span I could throw in a comment:
<span tal:omit-tag="python:True"
tal:content="python:utils.set_form_wins(request.client,False)">
Make sure that the history info is determined from the database and
that form values don't bleed over.
<span>
that is not possible using define. Any ideas on how to document this
use of define?
-- rouilj |
|
Date |
User |
Action |
Args |
2021-05-26 01:35:23 | rouilj | set | messageid: <1621992923.71.0.220704345693.issue2550964@roundup.psfhosted.org> |
2021-05-26 01:35:23 | rouilj | set | recipients:
+ rouilj, jerrykan |
2021-05-26 01:35:23 | rouilj | link | issue2550964 messages |
2021-05-26 01:35:23 | rouilj | create | |
|