Hi Joerg,
Didn't you say in another thread it works as expected in Firefox - a
browser
supporting XHTML?
Yes, but that was only in reference to the in-built xhtml serializer, which
as we know doesn't really xhtml serialize, and not the one from blocks which
doesn't quite like javascript!
--
On 19.03.2007 14:41, Jason Johnston wrote:
Yes, I only fixed the html serializer and that fix is not appropriate
for the xhtml. In html, the contents of the script tag is defined as a
cdata section, therefore there should be no encoding inside the script.
And that's what I fixed.
With xhtml the
On 19.03.2007 17:37, Jason Johnston wrote:
Well... sort of. When Firefox uses the XML parser the document gets
parsed just fine, but then another problem arises when the Dojo
libraries used by CForms AJAX tries to call document.write(), which
is not allowed in the XHTML DOM. So you trade a pro
On Mon, 19 Mar 2007 15:28:10 + (UTC), Joerg Heinicke <[EMAIL PROTECTED]>
wrote:
> Andrew Madu gmail.com> writes:
>
>> Wouldn't xhtml serializer need to be fixed anyway, as anyone using it as
>> serializer will still encounter the problems with javascript
> irrespective of
>> whether they are
Andrew Madu gmail.com> writes:
> Wouldn't xhtml serializer need to be fixed anyway, as anyone using it as
> serializer will still encounter the problems with javascript irrespective of
> whether they are using ajax forms or not?!!
Didn't you say in another thread it works as expected in Firefox
Hi Jason,
Well since Jörg is so strongly against it, and I don't feel like
swimming upstream against his opinion, I'm not going to bother. If you
still feel like taking that on (both the code and the argument) feel free.
Wouldn't xhtml serializer need to be fixed anyway, as anyone using it
Carsten Ziegeler wrote:
Jason Johnston wrote:
Carsten Ziegeler wrote:
Actually I was too fast in answering :(
Yes, I only fixed the html serializer and that fix is not appropriate
for the xhtml. In html, the contents of the script tag is defined as a
cdata section, therefore there should be no
On 17.03.2007 16:43, Jason Johnston wrote:
If by "the lazy guys" you also mean Cocoon itself. For instance, the
CForms forms-field-styling.xsl creates all its output in the null
namespace, which is fine for regular HTML delivery but if for some
reaason you do want to deliver as XHTML you have
Jason Johnston wrote:
> Carsten Ziegeler wrote:
>> Actually I was too fast in answering :(
>>
>> Yes, I only fixed the html serializer and that fix is not appropriate
>> for the xhtml. In html, the contents of the script tag is defined as a
>> cdata section, therefore there should be no encoding in
(moving to dev list)
On 16.03.2007 14:58, Jason Johnston wrote:
Another option might be to wrap the contents of elements
within a CDATA section so the JS could remain unencoded but it would
still result in well-formed XML. I'm not sure how some browsers
would hand
Carsten Ziegeler wrote:
Actually I was too fast in answering :(
Yes, I only fixed the html serializer and that fix is not appropriate
for the xhtml. In html, the contents of the script tag is defined as a
cdata section, therefore there should be no encoding inside the script.
And that's what I f
Joerg Heinicke wrote:
Jason Johnston lojjic.net> writes:
The first issue is that XHTMLSerializer encodes all double-quotes in
text content as ", which is of course absolutely valid XML/XHTML.
Unfortunately, when an XHTML document is served up with a text/html
mime-type, as you're doing, Fire
Hi Carsten,
I definitly think that we should fix this in the serializer by adding a
"/* */" before the
script tag closes. Additionally no encoding inside the script tag (as
with the html serializer).
Does this make sense?
Sounds good to me. I am of the opinion that ajax-request should be ro
Jason Johnston lojjic.net> writes:
> The first issue is that XHTMLSerializer encodes all double-quotes in
> text content as ", which is of course absolutely valid XML/XHTML.
> Unfortunately, when an XHTML document is served up with a text/html
> mime-type, as you're doing, Firefox doesn't actu
Actually I was too fast in answering :(
Yes, I only fixed the html serializer and that fix is not appropriate
for the xhtml. In html, the contents of the script tag is defined as a
cdata section, therefore there should be no encoding inside the script.
And that's what I fixed.
With xhtml the conte
I've done some investigation.
The first issue is that XHTMLSerializer encodes all double-quotes in
text content as ", which is of course absolutely valid XML/XHTML.
Unfortunately, when an XHTML document is served up with a text/html
mime-type, as you're doing, Firefox doesn't actually parse th
Hi Jörg,
Carsten fixed something in the HTMLSerializer, but changed nothing in
the XHTMLSerialzer:
Yes, I have seen the changes made by Carsten in HTMLSerializer:
@version CVS $Id: HTMLSerializer.java 515096 2007-03-06 12:11:29Z cziegeler
Changes to the XHTMLSerializer were made last by C
On 15.03.2007 18:43, Andrew Madu wrote:
thanks for the link. I checked out the latest files from the address given,
rebuilt cocoon, but the problem still remains. Carsten could you confirm
with me where exactly your changed files are or even better could you send
me the serializer.jar file?
Ca
Hi Bertrand,
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/
thanks for the link. I checked out the latest files from the address given,
rebuilt cocoon, but the problem still remains. Carsten could you confirm
with me where exactly your changed files are or even better could you
On 3/15/07, Andrew Madu <[EMAIL PROTECTED]> wrote:
...I have checked out the latest files from svn:
https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.1/RELEASE_2_1_10/..
the latest 2.1.x code is available at
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/
-Bertrand
-
Hi Carsten,
Yes, this is a bug in 2.1.10 - I have fixed it last week. You could
either use the current xhtml serializer from svn or wait for the next
release :)
For a second there I was almost convinced that you had sent your reply even
before I had sent my bug report! ;-)
I have checked ou
Yes, this is a bug in 2.1.10 - I have fixed it last week. You could
either use the current xhtml serializer from svn or wait for the next
release :)
Carsten
Andrew Madu wrote:
> Hi,
> I would like to bring this to the attention of the cocoon membership.
> Utilising the serializer block as seraliz
Hi,
I would like to bring this to the attention of the cocoon membership.
Utilising the serializer block as seralizer of choice in an ajax-request
block breaks the ajax process:
23 matches
Mail list logo
