Open Bug 88953 Opened 23 years ago Updated 2 years ago

Editing a page with document.writeln(<html><body>foopy</body></html> gives blank page

Categories

(Core :: DOM: Editor, defect)

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

People

(Reporter: sfraser_bugs, Unassigned)

References

(
URL
)

Details

(Keywords: helpwanted) 

If you load www.macromedia.com (I didn't have the Flash plugin intalled), and do 
Edit page, composer comes up with what looks like a blank page. But if you view 
the HTML source, you'll notice that there is a bunch of JS etc in there.

The trouble is that the JS on the page does a document.writeln to create the page 
contents, based on what plugins you have installed, and we turn off JS in the 
editor.

We need some kind of indication to the user that something is happening here, 
otherwise they might think that they just got about:blank, and start editing it 
as if it was a clean document.
1.0
Priority: -- → P3
Target Milestone: --- → mozilla1.0
duplicate of #85242?

No. This bug happens because we *do* disable JS (so the document.writelns never 
create the content).

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Over to editor folks.
Assignee: sfraser → akkana
What *should* the editor do here?  As far as we're concerned, it really is a
blank page.  Do you see the JS if you go into the source view?

(Cc'ing Beth as well as other editor folks because she usually has good
instincts about problems like this and might have a suggestion.)
I think the editor should put up a dialog telling the user that the page has 
dynamically-generated content. Imagine the scenario:
* User sees pretty page on the net, wants to clone it for own website
* User chooses 'Edit page'
* Page loads in composer, but looks totally different (because most of page
  content was document.written)
* User is confused.

Fine so far ...  When should we put up this dialog?  For any page that has a
script tag in it?  That has a script tag inside the body?  Are there any other
tags besides script that we should consider as dynamic?
I would suggest for any page that has script that does document.writeln, or 
document.write. But, I guess, that script could be in an external JS file, and 
you don't want to have to load and parse every script file. Hrmm. I wonder if 
there is some way we can get Gecko to tell us whether the page has script-
generated content.

removing myself from the cc list
->Future until we have some idea what to do here.
Keywords: helpwanted
Target Milestone: mozilla1.0.1 → Future
This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".
I don't think this is a mac-specific bug at all.  -->All/All
OS: Mac System 8.5 → All
Hardware: Macintosh → All
QA Contact: sujay → editor
This bug hasen't been touched for years and is clearly unowned. Moving back to default assignee/QA so that people, who are watching those can accurately triage this bug.

Also resetting Priority, Target Milestone, Status Whiteboard and Status.
Assignee: akkzilla → nobody
Priority: P3 → --
Target Milestone: Future → ---
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.