Closed Bug 20137 Opened 25 years ago Closed 25 years ago

Certain CSS + new drow down menu

Categories

(Core :: Layout, defect, P3)

x86
Other
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: tapio.markula, Assigned: troy)

References

()

Details

BAD! Incorrect display of my pages:
- scroll bars in frames even if scrolling should be off
- make table borders even if border should be zero; okay this can be fixed by using 'border:none' property
- drop-down menus seems strange - I can' touch the scroll bars! The starting text can't be seen totally; doesn't work properly
- CSS errors like in the daily build; following CSS doesn't work properly:
 table a strong, table a:link strong, table :visited strong, table :hover strong,  table :active strong, table :focus strong {display:block;width:50px;text-decoration:none;text-align:center}
a strong.s2,  :link strong.s2, :visited strong.s2, :hover strong.s2,  :active strong.s2, :focus strong.s2 {display:block;width:100%;text-decoration:none}
in my home page: http://www.nic.fi/~tapio1/

text links below the image links don't work as they should. The same happens to some other links too. Links looks differently before and after  I have touched the page. Something really strange. 'display:block' ???

ul li position works however

Crash with the same test pages as daily build.



Microsoft IE 5.0 displays many times better. Last builds are much WORSE than earlier builds.

It seems that Mozilla fails to make a proper browser. Sad.
The ONLY positive matter in Milestone 11 is that it works faster. It is really sad, that the only relative - just relative, not good - CSS2 implementation is in MS IE browsers.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Rejecting this bug report because there are at least 5 different
(unrelated) problems reported in this one bug report. It's going to be impossibe
to verify that all the different pieces of this bug are actual bugs and then are
fixed

Each bug needs to be reported as a separate bug report, and we need clearly
defined test cases

BTW, just because IE5 displays it a certain way doesn't mean that is correct.
You know that. Just like at David Baron's or Ian's test pages...
Status: RESOLVED → VERIFIED
Based on troy's comments, marking as verified invalid.
You need to log in before you can comment on or make changes to this bug.