The problem occurs where you want include the value of a variable inside an
attribute.
For example:
input type=string tal:attributes=value someValue
By default Page Templates replaces the escaped value in the form, unless
structure is specified. If someValue contained a (eg: test with a
But why? Why escape double quotes when it's not a reserved character?
I really don't understand the need, and the example in the collector
doesn't convince me. What is the problem?
Escaping quotes is needed in double quotes-delimited attributes but not
elsewhere.
Florent
On Mon, 2002-12-23 at
Andy McKay wrote:
Collector number 735: http://collector.zope.org/Zope/735
This was prompted by some bugs people found with Plone. For a two character
fix that to me looked like a simple oversight I didn't bother with a unit
test.
I'm not going to comment on whether or not page templates
Andy McKay wrote:
Collector number 735: http://collector.zope.org/Zope/735
This was prompted by some bugs people found with Plone. For a two character
fix that to me looked like a simple oversight I didn't bother with a unit
test.
*bzzzt* bad.
Everything should be unittested, please correct
Thanks a lot. However it doesn't test the case you describe below, does
it?
Its just tests that a is always escaped.
(And if it's a fix it should be in HEAD too.)
Why?
Well, because otherwise 2.7 won't have the fix :-)
Really, so all the changes and bug fixes done for 2.6.1 have to
Collector number 735: http://collector.zope.org/Zope/735
This was prompted by some bugs people found with Plone. For a two character
fix that to me looked like a simple oversight I didn't bother with a unit
test.
--
Andy McKay
- Original Message -
From: Florent Guillaume [EMAIL