Closed
Bug 2572
Opened 26 years ago
Closed 26 years ago
http://www.nasa.gov : Portion of main table should be restricted to 600 pixel width
Categories
(Core :: Layout: Tables, defect, P2)
Tracking
()
VERIFIED
FIXED
M4
People
(Reporter: christinehoff4, Assigned: rickg)
References
()
Details
Using 1/21 build on Win 95, Win NT, Win 98 and Mac 8.5 (linux not tested but
will followup).
Bring up URL.
There are several tables on the page. The main table incorporates everything
beneath the 3 images at the top. At the bottom of the page, there are three
sections: 'Cool NASA Websites', 'Other Cool NASA WebSites', and the Author
section.
Expected result: The three sections mentioned above should expand only 600
pixels in width from the left margin (they are part of the main table).
Actual results: These sections span the entire width of the screen.
Comment 1•26 years ago
|
||
To save some time, I'll point out that the 'over-width' of the page is caused
by the text links section (i.e., FAQ, Hot Topics, Multimedia ...).
Basic issue is what to do with a nested <NOBR>; in some ways, www.nasa.gov
is getting what they specified (but not what they intended).
Nav4 appears to terminate the first <NOBR> when the first </NOBR> is reached.
In other words, Nav4 doesn't try to nest the <NOBR> tags.
<HTML><BODY>
<!-- this is verbatim HTML from www.nasa.gov. Notice that in NGLayout, the
first NOBR applies to the entire set of anchor texts (i.e., entire line does
not break -->
<CENTER><NOBR> <!-- this NOBR is the "problem" -->
<font face="Helvetica, Arial" size="2">
<NOBR>[<A HREF="/qanda/index.html">Frequently Asked Questions</A>]</NOBR>
<NOBR>[<A HREF="/hotopics/index.html">Hot Topics</A>]</NOBR>
<NOBR>[<A HREF="/gallery/index.html">Multimedia Gallery</A>]</NOBR>
<NOBR>[<A HREF="/ntv/">NASA Television</A>]</NOBR>
<NOBR>[<A HREF="/textonly.html">Textonly Version</A>]</NOBR>
<NOBR>[<A HREF="/private.html">NASA Privacy Statement</A>]</NOBR>
<NOBR>[<A HREF="/siteindex.html">Site Map</A>]</NOBR>
<BR></CENTER></font>
</BODY></HTML>
(Tested with nightly Jan-21-99 build, Win95, optimized)
Comment 2•26 years ago
|
||
... and then it felt like deja vu all over again ... Ummm, this is a duplicate
of #1585 (and the description is identical to what I sketched out above), but
#1585 is marked FIXED (Jan 09) and VERIFIED (Jan 21) ... I'll leave it to the
Reporter: to sort out what to do with this.
Summary: [PP] http://www.nasa.gov: Portion of main table should be restricted to 600 pixel width → [PP]Jan25:http://www.nasa.gov: Portion of main table should be restricted to 600 pixel width
This bug still occurs with Win Jan 25 build. chrisd, need to know the results
against Mac and Linux too.
Updated•26 years ago
|
Hardware: PC → All
Comment 4•26 years ago
|
||
reproducible on MacOS 8.5 with 01/22/99 (most current) build.
reproducible on Linux rh5.2 with 01/25/99 (most current) build.
changing platform field to reflect cross-platformness of bug
Comment 5•26 years ago
|
||
installing myself as QA Contact for sevaral bugs at once
Updated•26 years ago
|
Summary: [PP]Jan25:http://www.nasa.gov: Portion of main table should be restricted to 600 pixel width → http://www.nasa.gov: Portion of main table should be restricted to 600 pixel width
Comment 8•26 years ago
|
||
Happened on all platforms. Removing from [PP] list, chrisd, please test with
latest build.
Comment 9•26 years ago
|
||
This is set to HTMLTables component, but it is not a table issue at all. This
should probably get re-assigned (component and engineer).
Updated•26 years ago
|
Assignee: karnaze → rickg
Comment 10•26 years ago
|
||
Rick, the comments indicate that it may be a parser related bug dealing with the
<NOBR>.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 11•26 years ago
|
||
Fixed by changes to CNavDTD.
Updated•26 years ago
|
Status: RESOLVED → REOPENED
Comment 12•26 years ago
|
||
The page is actually worse now but I believe it to be a different table related problem. I've filed this as bug 4576. I'm temporarily
reopening this bug until you look at both.
Comment 13•26 years ago
|
||
claudius, have you tried with the latest build? Please put build number that
you test on in bugs for us. Helps know what's happening when..thanks!
Updated•26 years ago
|
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Comment 14•26 years ago
|
||
the aforementioned behavior was with 1999040608 with NT - It was in the other bug report (oops).
However, upon retrying with 1999040718 all seems to be well on NT. Linux and mAc have other probs,
but not this bug.
Marking FIXED again.
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 15•26 years ago
|
||
marking VERIFIED with the very same 1999040608 build because the ..040718 build is blocking.
You need to log in
before you can comment on or make changes to this bug.
Description
•