Build: 2000121514, Mac OS 9.0 Various menu items are inappropriately enabled when viewing <about:blank> (this includes when a new blank window is opened). These items are: * `File' > `Save As ...' * `File' > `Print ...' * `File' > `Edit Page' * `File' > `Send Page ...' * `File' > `Send Link ...' * `File' > `Print ...' * `Edit' > `Select All' * `View' > `Reload' * `View' > `Page Source' * `View' > `Page Info' * `View' > `Translate' * `View' > `Character Coding' * `Search' > `Find in this Page ...' * `Search' > `Find Again' * `Tasks' > `Privacy & Security' > `Cookie Manager' > `Allow Cookies from this Site' * `Tasks' > `Privacy & Security' > `Cookie Manager' > `Block Cookies from this Site' * `Tasks' > `Privacy & Security' > `Image Manager' > `Allow Images from this Site' * `Tasks' > `Privacy & Security' > `Image Manager' > `Block Images from this Site'.

Netscape nav triage team: as per Alec Flett's pre-triage recommendation, this bug is nsbeta1-.

Editing about:blank is perfectly reasonable. as are Page Source and Page Info. imo save as is also reasonable. and i might want a blank or timestamped page so i want print. You might send someone a blank page. While reloading about:blank doesn't seem to make sense, when someone starts writing to it, it might. recommend resolve as invalid or wontfix. If you want us to treat "" as a non page then that's a different story, but for now we should treat all urls as real, special casing this one is ill advised.

I agree with timeless. I suggest this as a wontfix.

Thankyou, Timeless, for putting me in hysterics for a good five minutes when I read that comment. Just in case you were serious ... > Editing about:blank is perfectly reasonable. No it's not. If you want to start a blank page, the obvious (and quicker) route is `File' > `New' > `Blank Page'. You don't even know that about:blank is in a file type which Composer can handle. (application/x-nothingness?) > as are Page Source and Page Info. imo save as is also reasonable. and i might > want a blank or timestamped page so i want print. You might send someone a > blank page. Ditto. All of those are things which nobody except Timeless would ever want to do. And all of them can be more obviously achieved by selecting `File' > `New' > `Blank Page' and then choosing the appropriate command. > While reloading about:blank doesn't seem to make sense, when someone starts > writing to it, it might. But nobody ever will write to it. about:blank is blank, by definition. If people could write to it, that would be a more serious bug than this one. The fact that about:blank is currently a minimal HTML page is just an accident of implementation. As far as the user is concerned, about:blank consists of nothing at all, so it does not make sense for any file operations to be available for it. All leaving the items enabled does is let users waste time or make mistakes.

> If people could write to it, that would be a more serious bug than this one. about:blank is the standard page to open if you want to use document.write() to create a document. I don't think that's going to change, although I wouldn't mind trying to get rid of about:blank in the location bar after someone has used document.write() on the page. See bug 51844 for more discussion about about:blank, d.write(), and mime types.

Marking nsbeta1- bugs as future to get off the radar.

I agree with this bug that those items should be disabled, but I'm wondering if this would just be adding bloat. Are there other cases beside about:blank where we'd want to disable all these items (that might warrant setting up such a system)?

Blake, I think there are cases in navigator.js where we test to see if the currently viewed page is "about:blank". All you would have to do is to put some disabling fu in there.

The items which should be disabled for <about:blank> are a subset of the items which should be disabled when there are no windows open. I don't know how useful that is, though. IMO, if <about:blank> is a legitimate URI, it should be handled properly. Which means disabling menu items which don't apply.

about:blank is also loaded for the hidden window, so some of this applies to bug 75660.

navigator needs a controller. this isn't the only case in which inappropriate items are enabled. I believe all the other app windows have one.

spam: over to File Handling. i have not changed the assigned developer [or the other fields for that matter], so if anyone realizes that a bug should have a more appropriate owner, go ahead and change it. :)

(build 2002041408 win98) Actually I was about to post a bug *opposite* to this one... Why can't you save or handle otherwise "about:" pages? You could do that on Netscape up to v4.xx and you still can on IE 6 and Opera 6.

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".

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.

External programs have been hijacking about:blank for their own ends, and in diagnosing such problems, all those features could be useful. Bug should be marked invalid.