Sept. 22, 2014
12:35 p.m.
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