Not sure how or why you need the browser to render XML, so this may not help,
but I had this same issue a few months ago – I needed to render using the
browser for a class I was teaching on EAD and didn’t want to mess about with
browser security – and David Carlisle provided me with this very cool little
bare-bones html page:
https://library.syracuse.edu/digital/guides/lavender/student_files/test2.html
Michele
From: Wendell Piez wapiez(_at_)wendellpiez(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Friday, May 27, 2022 7:43 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Not able to render XML in Chrome browser
Hi,
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(_dot_)honnen(_at_)gmx(_dot_)de<mailto:martin(_dot_)honnen(_at_)gmx(_dot_)de>
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com<mailto:xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>>
wrote:
Am 27.05.2022 um 06:19 schrieb Joga Singh Rawat
jrawat(_at_)aptaracorp(_dot_)com<mailto:jrawat(_at_)aptaracorp(_dot_)com>:
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<http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/xsl-list/174322> (by email)
--
...Wendell Piez... ...wendell -at- nist -dot- gov...
...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
...github.com/wendellpiez.<http://github.com/wendellpiez.>..
...gitlab.coko.foundation/wendell...
XSL-List info and archive<http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/xsl-list/1127818> (by
email<>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--