Domparser is not working in iFrame

Question

1.00/5 (1 vote)

See more:

Hi,

I have one textbox and a button. When I am entering all the special characters in textbox and clicked on button it should return me the same text which I entered in textbox. For this I am using DOMParser function which is working fine in IE but not in Iframme. My application opens in Iframe and need to fix this problem.

Kindly help.

Thanks.

What I have tried:

Not sure how to fox this issue in iFrames
as DOMParser is not for iFrame. Below is my code which is working fine in IE but not in iFrame.

Function parseText(string){
Var parser = new DOMParser;
Var dom = parser.parseFromString(
'<!doctype.html><body>'+ string,'text/html');
return dom.body.textcontext;
}

Posted 9-Nov-18 0:02am

Telstra

Updated 9-Nov-18 2:45am

v3

Add a Solution

Comments

CHill60 9-Nov-18 6:08am

Not sure how we can fix any problem without seeing any code

F-ES Sitecore 9-Nov-18 6:19am

You're either using DOMParser incorrectly (we don't know as we can't see your code) or the issue is that the site in the iframe is from a different host as the one your js is on as the browser won't let you script against sites from a different host.

Telstra 9-Nov-18 6:30am

Hi F-ES Sitecore,

Both iframe and js are on the same domain.

Thanks,
Nilesh

Telstra 9-Nov-18 6:20am

Function parseText(string){
Var parser = new DOMParse;
Var dom = parser.parseFromString(
'<!doctype.html>'+ string,'text/html');
return dom.body.textcontext;
}

Richard MacCutchan 9-Nov-18 6:31am

Please edit your question and show the code there. Also explain exactly what happens when your code runs.

Telstra 9-Nov-18 6:39am

Hi Richard,

Thanks for reply. I have updated the question.

Richard Deeming 9-Nov-18 7:49am

"... explain exactly what happens when your code runs."

You missed that part. "Not working" doesn't tell us anything.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

W∴ Balboos, *GHB* · Answer 1 · 2018-11-09T02:45:00

You need to keep in mind that when you open an <iframe> on your page it is, for most purposes, a separate location from your regular page. Thus, depending upon where you call your DOM accessing functionality, you need to keep in mind that it will only look at it's own page - that is, it's own scope.

As an example, you may open a copy of a page inside of itself. It would then have the same id='' values in both the parent and child pages. The DOM can tell them apart because they are in "different scopes".

Note the use in the previous paragraph of 'parent' and 'child'. There is the ability to be in one scope and access the other using references to the parent or child.

So - depending upon where you request the data relative to where it is, you will see different results (like failure). Consider this - you may solve your problem.