Closed
Bug 3557
Opened 26 years ago
Closed 25 years ago
[PP]Page layout fails at naval clock content on this page
Categories
(Core :: Layout, defect, P1)
Tracking
()
VERIFIED
WORKSFORME
M10
People
(Reporter: glynn, Assigned: ramiro)
References
()
Details
(Whiteboard: fails still with Mar26 latest builds)
Linux 5.2, win98, Mac March 9 optimized seamonkey builds
1. Launch app and go to: http://www.ac2000.org
• Page does not layout, tries and stalls at the Naval Observatory Clock graphic.
I tried to use source pages to physically narrow down and other issues such as
illegal frameset html exist. If you simply load the home.html frame separately
the app will crash; on Mac with a (this holds the naval clock code).
On linux error in cmd line: Gdk=CRITICAL **; file gdkpixmap.c: line 820
(gdk_pixmap_unref): assertion `pixm!= NULL' failed.
Let's look at this sensibly for a minute: how can something that's Linux
specific and failing in the gdk code be a LAYOUT bug?
If you note, the bug occurs on ALL platforms. I cited the Linux result and
actually had started to cite some Mac info but it appears it was cut off on
entry. On Mac the page also does not layout; some of the frame source pages
have their own individual issues which cause crashes which are separate bugs and
being field as such.
Assignee: glynn → rickg
Summary: Unable to layout page due to pixmap = null → Page layout fails at naval clock content on this page
mmmmm...bug is now assigned to me directly with no comments as to why. I checked
the cited URL again with March 10 and 11 builds cross platform and it still fails
at same point when Naval Clock graphic is displayed and data access occurs. Old
summary was "Unable to layout page due to pixmap = null", adjusted summary to
reflect where it fails. Will attempt to narrow down more but as mentioned other
problems with source pages were preventing that a bit. Reassigned to rickg to
farm out to developer; he can adjust priority appropriately.
Updated•26 years ago
|
Target Milestone: M3 → M4
Comment 5•26 years ago
|
||
moving to m4
Ramiro -- please take a look. Things to consider: 1) there was a known problem
regarding transparent images on linux which may be an issue here. 2) There is a
crash, even on NT, in the view construction code if you resize the window. I'm
creating a new bug for Troy regarding that issue.
I tried this page on both nt and linux on march 26 build and it works fine on
both.
can you verify ? thanks.
Mar 26 optimized apprunner, Mac, Win98 and Linux 5.2, still stalls after clock
loads, leaving clock at top of content area, the left nav and main content area
items incompletely rendered and placed.
you are correct, i was not looking at the right thing.
need to investigate more.
Comment 10•26 years ago
|
||
this crashes as of april 5 as a debug linux build
Assignee | ||
Updated•26 years ago
|
Target Milestone: M4 → M5
Comment 11•26 years ago
|
||
m5
Summary: Page layout fails at naval clock content on this page → [PP]Page layout fails at naval clock content on this page
Assignee | ||
Updated•25 years ago
|
Target Milestone: M5 → M6
Comment 12•25 years ago
|
||
this page works the same on both viewer and apprunner on both win32 and linux.
can you find an XP owner for this ?
it would also be useful to figure out exactly why the clock thing isnt working
as expect, ie, isolate the html or JavaScript.
thanks
marking m6
Comment 13•25 years ago
|
||
m7
Assignee | ||
Updated•25 years ago
|
Target Milestone: M7 → M10
Comment 14•25 years ago
|
||
marking m10, this still is an XP bug.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Comment 15•25 years ago
|
||
just tried it, page lays out fine on linux.
If there are issues with the clock display, then you need to isolate that html
and file separate bugs for that.
markings worksforme.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 16•25 years ago
|
||
In the latest build Sept 2 (1999090208), the pages loads correctly on all
platforms tested: Mac 8.6, Win 95, Linux (Red Hat 6.0).
You need to log in
before you can comment on or make changes to this bug.
Description
•