176668 - [RFE] document.write, document.writeln not supported during transform

Status: RESOLVED INVALID

(Core :: XSLT, enhancement)

Description

[Markus Hübner]

Testing trunk build 2002102415 and going to
http://www.world-direct.com/gia/test/feedback.asp
doesn't display anything (works fine in other browsers).

When going to the URL the status bar says 'stopped' and
when clicking on the 'stop button' and taking a look
at the source code there is just the single line:
<link rel="stylesheet" type="text/css" href="wdstylens6.css">

This page works the way that an external JavaScript file (ext.js)
is doing a document.writeln(); depending on the used browser for
the CSS file to use.

There is no error in the JavaScript console.
This could be a regression of bug 130161.

Comment 1

[Markus Hübner]

Reassigning to Sicking as he dealt with that.

Comment 2

[Boris Zbarsky [:bzbarsky]]

What does this have to do with xslt?

This is broken in Oct 22 builds too, btw; do we have a regression date range? 
That's the first order of business...

Comment 3

[Axel Hecht]

this is not a regression.
document.write is not supported as being called during transforms.
And it won't be as long as we don't feed the result thru the parser.

Comment 4

[Markus Hübner]

This bug is not about a feature, rather than about a hanging mozilla.
Mozilla already worked on that page before --> reopening.

Comment 5

[Roland Sippel]

works for me
Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.2b) Gecko/20021018

Comment 6

[Emanuele]

it works for me (Mozilla 1.2b on Linux)

Comment 7

[Markus Hübner]

Using trunk build 2002111508 I still don't get anything displayed at
http://www.world-direct.com/gia/test/partner.asp

Comment 8

[Peter Van der Beken [:peterv]]

Can't see the testcase, please attach a simple testcase to the bug. Mozilla is
not hanging, it just doesn't display anything. If you're doing document.write
during the transform like Axel says then this bug has very low priority of
getting fixed, if ever.

Comment 9

[Markus Hübner]

The problem is that Mozilla doesn't show anything at all - Mozilla did show 
the output before. Why has this regressed?
Updating URL with a simpler testcase.

Comment 10

[Peter Van der Beken [:peterv]]

Attach a simple testcase. This has not regressed, if it worked before it was by
pure chance. As I said, there's very little priority for getting this fixed.
Please don't reply unless you're giving us a reduced testcase.

Comment 11

[Axel Hecht]

changing topic to make it actually say what this bug is about.
As there is no intention to support document.write, making nobody own this.

Comment 12

[Axel Hecht]

I wonder if we could shadow document.write and document.writeln with
function(){
  alert("document.write[ln] not supported during XSLT transformations.");
}

Thus we wouldn't call document.open, which is causing the crash in 202765, AFAICT.
And it would be less cryptic for users of these.
I bet it's possible to do that, it might be trickier to unshadow the functions
after the transformation, though.

Comment 13

[Axel Hecht]

If we ever reconsider the decision to not support document.write, we should
reconsider support of output-escaping as well. Those are just the same things with
different hookups. See bug 98168.

Comment 14

[Phil Ringnalda (:philor)]

*** Bug 276224 has been marked as a duplicate of this bug. ***

Comment 15

[Markus Hübner]

Is there a reduced testcase still needed?

Comment 16

[Bence Varga]

I can understand your point not to support document.write, but it works (of
course) in case of server-side processing. My goal was to lessen the load on the
server.

Incidentally it would use something like

if (document.body.clientWidth < 990)
	document.write ("<" + "!--");

and while the body tag is not present (bug 276222) it doesnt make any use anyway.