Closed
Bug 1668
Opened 26 years ago
Closed 26 years ago
document.writeln() calls should append newline before calling parser
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Tracking
()
VERIFIED
FIXED
People
(Reporter: rickg, Assigned: vidur)
Details
Today, when document.writeln() is called, it calls the parser with its text
argument. Then, it calls again with plain newline. These should be combined so
that the newline gets to the parser as part of the text. This will improve
performance.
|
Assignee | |
Updated•26 years ago
|
Status: NEW → ASSIGNED
|
|
Assignee | |
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 1•26 years ago
|
||
Fixed
I've tried the following file to measure any performance difference between
the Development Preview build (11/30/98) and viewer M3 build (3/18/99):
<HTML>
<HEAD>
<TITLE>MyPage</TITLE>
</HEAD>
<BODY>
<SCRIPT TYPE="text/javascript">
var i = 0;
dStart = new Date();
for (i=0; i<1000; i++) {
document.writeln("a");
}
dEnd = new Date();
document.write((dEnd.getTime() - dStart.getTime())/1000);
</SCRIPT>
</BODY>
</HTML>
It shows a performance improvement from 0.42 sec. to 0.34 sec on my WinNT
machine. Once the document is cached, the test result deviation is minimum (very
reliable).
Although this measure may not be meaningful because many other factors, I'm
marking this bug as verified. Please let me know if you consider it should be
verified in some other way, or if you'd like to provide a testcase to verify it.
|
||
Updated•18 years ago
|
Flags: in-testsuite-
|
|
||
Comment 3•18 years ago
|
||
denying in-testsuite since it isn't detectable from DOM/JS
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•