Question

155

Why isn't chrome running this javascript

rated 0 times [ 158] [ 3] / answers: 1 / hits: 17359 / 15 Years ago, fri, april 17, 2009, 12:00:00

When I run this in Chrome (ver 2), it doesn't return the string, but it works in Firefox (ver 3). Why is this?

<html>

<head>

<script type=text/javascript>

function disp_prompt() {

    var name=prompt(Please enter your name,Harry Potter);

    if (name!=null && name!=) {

        document.write(Hello  + name + ! How are you today?);

    }

}

</script>

</head>

<body>



<input type=button onclick=disp_prompt() value=Display a prompt box />



</body>

</html>

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

bobbyallanh

Add To Favorites

Follow

Total Points: 693

Total Questions: 120

Total Answers: 101

Location: Bermuda

Member since Thu, Apr 20, 2023

1 Year ago

bobbyallanh questions

1 chrome extension: Uncaught TypeError: Cannot read properties of undefined (reading 'onClicked')

Tue, Jan 25, 22, 00:00, 2 Years ago

1 How can I add ellipses (...) for longer text in an AgGrid?

Thu, Oct 14, 21, 00:00, 3 Years ago

1 Using FormData() inside fetch api is not working

Mon, Jun 29, 20, 00:00, 4 Years ago

1 Undefined on localStorage.getItem in Angular

Tue, Jun 16, 20, 00:00, 4 Years ago

1 How to dynamically change button size and color in React

Mon, Jan 27, 20, 00:00, 4 Years ago

View All

answered 15 Years ago amari · Accepted Answer

To append content to a document, you should only call document.write() during the <script>-block parsing phase.

If you have a call to document.write somewhere where it executes outside that context, such as in your event handler, there is no parsing going on, so nowhere for that string 'foo' to go.

What should happen according to the original JavaScript reference is:

Event handlers execute after the original document closes, so the write method implicitly opens a new document of mimeType text/html if you do not explicitly issue a document.open method in the event handler.

That is, it assumes you've made a mistake and meant to do:

document.open('text/html');

document.write(html);

Which replaces the entire document with new content. You'll also notice that because you didn't finish that off by calling:

document.close();

...in Firefox, the ‘loading’ throbber is still animating, expecting more content to be written to the document (but it never comes).

In this case, you are document.write()ing a string:

Hello bobince! How are you today?

that is clearly not a valid HTML document. Chrome (and Safari, which behaves the same) is trying to parse it as an HTML document, but fails because it is non-whitespace text content outside the document element (<html>), which is not allowed. If you put some tags in the name input:

Hello <em>bobince</em>! How are you today?

You'll see everything outside the <em> element is discarded. Firefox and IE manage to apply their “fix up text outside any element” broken-HTML-rule to save you, but Chrome doesn't.

If you want to document.write() a new document, you should make sure it is indeed a complete document:

<html><head><title>Greetings</title><body><p>Hello bobince! How are you today?</p></body></html>

Or, if you want to document.write() a text string, you should theoretically call:

document.open('text/plain');

before the write(). But beware, the mimetype parameter is not supported by Chrome or Safari; they'll always treat what you write as HTML.

In any case, you probably don't want to be using this method. If you want to add to (or change) the existing page you should normally be using DOM methods, such as setting the text on a status output div, or replacing the body contents using innerHTML.

document.write() is needed in a few places (in particular, when you are creating a new window or frame from scratch), but otherwise it's generally the wrong thing and should be viewed with suspicion.