Safari and weird rendering
Maybe someone has had this. I see that when IE or Safari get a response from Seaside, I do get an application/xhtml+xlml returned. But with Firefox and Chrome, this is text/html; charset=utf-8 The server is Zinc HTTP Components 1.0 Why is there such a difference? I've put the preference in the app to force it but Zinc still serves the way described above. Ideas? Phil
On 22 Sep 2014, at 14:10, phil@highoctane.be wrote:
Maybe someone has had this.
I see that when IE or Safari get a response from Seaside, I do get an application/xhtml+xlml returned.
But with Firefox and Chrome, this is text/html; charset=utf-8
The server is Zinc HTTP Components 1.0
Why is there such a difference?
I've put the preference in the app to force it but Zinc still serves the way described above.
Ideas?
Phil
I do not understand exactly what you mean or want, in any case, the default Seaside response will be of type text/html; charset=utf-8. I would be quite surprised if there were differences per client (this is not impossible, but I don't think Seaside does that). Zinc has very little to do with this as you can see in ZnZincServerAdaptor>>#responseFrom: where the Seaside response object is converted. Sven
Ok, found why. SVGXHTMLBrowserAdapter still thinks Safari cannot do HTML5 and invoked beSVGXHTML which broke things. Phil On Mon, Sep 22, 2014 at 2:10 PM, phil@highoctane.be <phil@highoctane.be> wrote:
Maybe someone has had this.
I see that when IE or Safari get a response from Seaside, I do get an application/xhtml+xlml returned.
But with Firefox and Chrome, this is text/html; charset=utf-8
The server is Zinc HTTP Components 1.0
Why is there such a difference?
I've put the preference in the app to force it but Zinc still serves the way described above.
Ideas?
Phil
participants (2)
-
phil＠highoctane.be -
Sven Van Caekenberghe