Closed Bug 38432 Opened 25 years ago Closed 25 years ago

[regression] box no longer supports style of overflow:auto

Categories

(Core :: XUL, defect, P2)

defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: hangas, Assigned: eric)

References

Details

(Whiteboard: [nsbeta2+][dogfood-])

The address book window uses a style of overflow:auto on the box containing the card view. This is broken now and using this style causes all the elements in the card view pane to be drawn over each other. Removing this style fixes the drawing problem but then turns off the needed scrollbar on that pane. To reproduce: select a card in the address book window, the card view pane will be drawn in an unreadable way.
Nominating for nsbeta2 and dogfood. We shipped a working address book in beta1, we should not ship beta2 without this functionality.
Keywords: dogfood, nsbeta2
Putting on [nsbeta2+][dogfood-] radar. Does not need a fix ASAP for daily work, but we should fix this for beta2.
Whiteboard: [nsbeta2+][dogfood-]
reassigning to evaughan as p2 for m17
Assignee: trudelle → evaughan
Priority: P3 → P2
Target Milestone: --- → M17
Blocks: 40158
Hangas can you please direct me to the box that should have overflow auto on it so I can test this?
Status: NEW → ASSIGNED
I believe that it is the style on CardViewBox in addressbook.css (... skins/modern/messenger/skin/addressbook/addressbook.css) #CardViewBox { /* overflow: auto;*/ background-color: #EEEEEE; min-width: 150px; user-focus: ignore; } However, if I re-enable the overflow: auto, it looks fine to me. Is this working correctly now, hangas?
this is working for me too now. I also get the scrollbar back. It looks like this got fixed with someone else's fix. Marking WORKSFORME. I'll file another bug on myself to reenable overflow: auto.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
verified worksforme mac/linux/win32 20000525nn
Status: RESOLVED → VERIFIED
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.