Re: [Seaside] [Q] Ajax UTF-8 Problem in WebKit(Older one in AIR)

"S.J.Chun" chunsj at
Tue Apr 8 09:11:02 UTC 2008


I've reported this relevant bug to AIR team. What I want to know is
that whether there're some kind of work around for this past bug(yes,
it's ridiculous :-)

I'll just wait for next version of AIR. Anyway the performance of WebKit
in AIR is very good; for my application, it even surpasses IE7. (Don't say
to me that FF3/Safari is faster, for my application they're slower than IE7,
IE7 almost instantly displays my Ajax lightbox style dialog. The FF3/Safari
does have some hesitation before displaying. Funny thing is that at Mac OS X,
they does not show that "hesitation". I don't know why). 

----- Original Message -----
   From: Lukas Renggli <renggli at>
   To: ""S.J.Chun"" <chunsj at>, Seaside - general discussion <seaside at>
   Sent: 08-04-08 15:36:07
   Subject: Re: [Seaside] [Q] Ajax UTF-8 Problem in WebKit(Older one in AIR)

  >  The problem is that when I render the content of anID not using Ajax update, it
>  just renders itself correctly. But with above code, the rendered UTF-8 korean string
>  is broken. I have no problem with current safari, firefox, ie; only ooold safari 2.0.X and
>  AIR(which uses unfixed version of webkit) does show this problem.

It looks to me like you should ask this question in an AIR
mailing-list/forum. I don't think it has anything to do with
prototype, as this library just inserts the strings into the DOM tree
as they arrive through XMLHTTPRequest. Maybe you can patch the updater
so that it changes the encoding in JavaScript?


Lukas Renggli

More information about the seaside mailing list