Re: [xsl] Not able to render XML in Chrome browser

Subject: Re: [xsl] Not able to render XML in Chrome browser
From: "Wendell Piez wapiez@xxxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 27 May 2022 11:42:57 -0000

Don't forget, to go to the effort of circumventing the restrictions on the
browser imposes its own kind of overhead, to say nothing of risks. (Which,
like most risks, may or may not be risks for you.)

I also agree with Norm that running a server these days is not actually so
hard; moreover this is a useful thing to know about.

The browsers have not stopped honoring CSS have they? It is much more
capable than it was in the bad old days.

Cheers, Wendell

On Fri, May 27, 2022 at 5:32 AM Martin Honnen martin.honnen@xxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Am 27.05.2022 um 06:19 schrieb Joga Singh Rawat jrawat@xxxxxxxxxxxxxx:
> I have checked with F12/ developer console, it is showing security
> warning. But it is working fine with other Browser except Chrome.
> Well, unless you share details about the way you load the XML (over the
> file system or over HTTP(S)), the exact error message or warning you get,
> the exact version of Chrome you use and for any other browsers (besides IE
> that never had that restriction) you want to talk about the exact versions
> you use I don't see how we can help to explain it.
> To my knowledge Edge exists in two very different versions, one being the
> now old but Microsoft built one, that, as far as I remember, did not have
> the restriction. The current Edge is based on the Chromium browser and has
> the restriction.
> Firefox has had the restriction for a rather long period of about two
> years I think if we talk about the current release; on the other hand,
> until some months ago, it allowed you to work around the restriction with
> some preference which is no longer supported.
> XSL-List info and archive <>
> EasyUnsubscribe <> (by
> email <>)

...Wendell Piez... ...wendell -at- nist -dot- gov...

Current Thread