Closed Bug 3396 Opened 26 years ago Closed 26 years ago

Text does not appear on the screen

Categories

(Core :: Layout, defect, P1)

Product:
Core
Component:
Layout
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: morse, Assigned: harishd)

Details

Following content does not display the text on the screen. Not a blocking problem for wallet development but an anoyance none-the-less. <HTML> <HEAD> <SCRIPT> function loadFrames(){ top.frames[1].document.open(); top.frames[1].document.write ("This message doesn't appear on the screen."); top.frames[1].document.close(); }; </SCRIPT> </HEAD> <FRAMESET ROWS = 25,25 onLoad=loadFrames()> <FRAME SRC=about:blank> <FRAME SRC=about:blank> </FRAMESET> <NOFRAMES> <BODY> <P> </BODY> </NOFRAMES> </HTML>
Product: MozillaClassic → Browser
Version: 1998-03-31 → other
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Assignee: pollmann → harishd
Dup of one of your bugs, I believe...
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
This problem is related to <script> tag, inside head, opening <body> tag and therefore ignoring the <frameset>. Fix was checked in, on Mar 17, and the text now appears on the screen. Marking the bug fixed.
Status: RESOLVED → CLOSED
Status: CLOSED → VERIFIED
Fixed in the March 23rd Build.
Fixed in the March 23rd Build.
Severity: normal → critical
Status: VERIFIED → REOPENED
Priority: P2 → P1
Reopening. The fact that the bug appeared to be fixed was only an illusion. Change the [1] to [0] (in three places) and then you get the javascript error message: Javascript error: top.frames[0] has no properties. In fact, if you add a few more frames to the frameset and then use some other index besides 1, you will get the same error. In all cases in which you get the error message, you at least get the frames painted although the message does not appear in any of them. In the case in which you do not get the error message (i.e., when using index 1), you get the message but you don't get any of the frames. So even that case is not working properly. This is high priority because although it wasn't blocking wallet implementation, it is now blocking the implementation of the cookie viewer and the single signon viewer.
Target Milestone: M5
Setting M5 milestone.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
As of this mornings build, this is miraculously working. So I'll close out this bug report. However this opened the door for me to go further and discover three more bugs, one of which is still blocking me. See reports 5409, 5410, and 5411. The blocking one is 5410.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.