Closed Bug 716 Opened 27 years ago Closed 26 years ago

nested cssp bug

Categories

(MozillaClassic Graveyard :: Layout, defect, P1)

1998-07-28
x86
Windows 95

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: garys, Assigned: pollmann)

References

()

Details

In most cases, you can't nest cssp elements. This is a major bug for developers, because it is absolutely necessary to nest elements/layers for creating certain D-HTML content. (note that you can nest cssp elements in IE without it breaking like it does in dogbert.) See the sample URL. Notice that the first nest of elements works fine, but then the following nests of the cssp layers somehow loose their cssp properties or something... Please fix this! If you have any questions, let me know. -Gary
Setting target fix to 5.0 and assigning this to djw who is working on CSS stability.
Downgrading priotity to P1.
Reassigning to eric pollmann
The problem seems to be: The document.ids hashtable gets created twice. By chance, the two are used correctly for a while, but when the first div closes, every other element after that has its style struct defined in one hash table then looked up in the other. This causes the style struct to not be found when the tag is pushed on the style stack: - Add id0 to table 00a7e540 Find id0 in table 00a7e540 - Add id1 to table 00a82ee0 Find id1 in table 00a82ee0 - Add id2 to table 00a82ee0 Find id2 in table 00a82ee0 - Add id3 to table 00a82ee0 Find id3 in table 00a82ee0 - Add id4 to table 00a7e540 Find id4 in table 00a82ee0 (Style struct not found) - Add id5 to table 00a7e540 Find id5 in table 00a82ee0 (Not found) - Add id6 to table 00a7e540 Find id6 in table 00a82ee0 (Not found) - Add id7 to table 00a7e540 Find id7 in table 00a82ee0 (Not found) - Add id8 to table 00a7e540 Find id8 in table 00a82ee0 (Not found) ...
Component: mail/news → Layout
Version: other → 1998-07-28
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
This seems to be fixed with nglayout. The positioning is correct. Marking resolved.
QA Contact: 4110
Chris -- please verify
Status: RESOLVED → VERIFIED
Using 2/5 build verified fixed.
You need to log in before you can comment on or make changes to this bug.