http://www.rsac.org has scrolling problems (possible parser error)

VERIFIED FIXED in M4

Status

()

Core
Layout
P2
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: phillip, Assigned: rickg)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
build 98112312 "Nov_23a", xpviewer.exe on NT4.0

the banner (enclosed in <IFRAME></IFRAME> tags does not show up at all, but
the area where it should be drawn "picks up" pixels from whatever window
you slide in front of it.

also, the table lays out with a big gif with a black padding area twice as
high and wide as the gif, which is very different from what 4.x renders.
if you drag the window wide enough, there are ghost black rectangles in a
column.

i'm unsure whether this is stuff for HTMLTables or just Layout...

Updated

19 years ago
Summary: ss: site #55 has banner/table layout problems → ss: http://www.rsac.org has banner/table layout problems

Updated

19 years ago
Assignee: kipp → karnaze

Comment 1

19 years ago
It displays fine for me.

However, it crashes pretty easy because of a bug in the frameset event handling
code. I'm CC'ing tom because the crash occurs after having let go of the scroll
bar and then wandering into the frame cell...

Comment 2

19 years ago
I've fixed the crash in the frameset code and will check it in when the build is
green again. I think some of the changes in the event handling code may be
causing the frameset frame to get events it didn't expect.

I'm seeing a scrollbar around the whole document which is wrong, but I have a
build that is more than a day old.

Updated

19 years ago
Assignee: karnaze → rickg
Summary: ss: http://www.rsac.org has banner/table layout problems → ss: http://www.rsac.org has scrolling problems (possible parser error)

Comment 3

19 years ago
The main frameset document has a scrollbar which is incorrect. There is a
<noframes> inside of a <frameset> and the <noframes> contains a <body>. The
content sink's openBody method is getting called before its openFrameset which
shouldn't be the case. The parser may be getting confused and processing the
<body> which is inside the <noframes>.

I've changed the summary of the bug.

Updated

19 years ago
Summary: ss: http://www.rsac.org has scrolling problems (possible parser error) → http://www.rsac.org has scrolling problems (possible parser error)

Comment 4

19 years ago
Taking off ss: list per bug mtg today.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 5

19 years ago
Setting all current Open/Normal to M4.

Comment 6

19 years ago
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)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Summary: http://www.rsac.org has scrolling problems (possible parser error) → http://www.rsac.org has scrolling problems (possible parser error)
(Assignee)

Comment 7

19 years ago
I believe this is fixed now.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 8

19 years ago
Fixed in April 6th Build.
You need to log in before you can comment on or make changes to this bug.