(I wrote this Friday but just realized I failed to include the
listserv in my reply.)
Thanks so much for the quick replies, and sorry to bring up an old
debate. My bad for not searching the archives well enough.
In my case I was generating the URL for use in a plain-text e-mail,
so
I seem to have encountered a bug in
WOContext.directActionURLForActionNamed(). When I pass it a query
dictionary containing more than one key, it returns a string in which
the query arguments are separted by 'amp;' instead of just an
ampersand. As a result, if I pass a query dictionary
Not really sure I want to step into this... :-)
On Apr 26, 2006, at 3:49 PM, Nathan Hadfield wrote:
I seem to have encountered a bug in
WOContext.directActionURLForActionNamed(). When I pass it a query
dictionary containing more than one key, it returns a string in
which the query
David LeBer, Nov 15 2005 says a quick Mail search ... This teeters on
a religious debate I believe :) It comes down to how you are using
the result of that method. If you use it inside of an a href =
.. then it's SUPPOSED to be escaped (to be XHTML compliant).
However, apparently it
On Apr 26, 2006, at 5:32 PM, Mike Schrag wrote:
So basically, if you were expecting it the old way, it's broken,
but if you thought it was broken before, it's fixed :)
ROFL!
--
Coming in late 2006 - an introduction to web applications using
WebObjects and Xcode
On 26-Apr-06, at 8:32 PM, Mike Schrag wrote:
David LeBer, Nov 15 2005 says a quick Mail search ... This teeters
on a religious debate I believe :) It comes down to how you are
using the result of that method. If you use it inside of an a
href = .. then it's SUPPOSED to be escaped (to be
