Closed
Bug 178837
Opened 22 years ago
Closed 20 years ago
Scrollbar inconsistency between themes (-moz-scrollbars-vertical)
Categories
(SeaMonkey :: Themes, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ruud, Assigned: shliang)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021105 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021105 Please view the test page with the Classic and Modern themes. On this page, the overflow property (value: -moz-scrollbars-vertical) has been used. If not applied, Netscape 7 and Chimera 0.6 do not display a scrollbar. If applied, the page shows properly in Mozilla 1.2b (build 2002110508) in the Modern theme. However, the Classic theme displays the page as Netscape and Chimera do: a scrollbar appears but is inactive and inconsistent with the layer content. Reproducible: Always Steps to Reproduce: 1. Apply Classic theme 2. Visit http://www.eti.uva.nl/ruud_temp/mozilla.html Actual Results: Inconsistent display of vertical scrollbar. Expected Results: Display scrollbar as in Modern theme.
Comment 1•22 years ago
|
||
I see it too and it looks correct with the Orbit3+1 theme. The thing that ties this all together is that Chimera and the Classic theme both use the Mac OS X "aqua" scroll bars. But I think the problem is really with your stylesheets. The problem goes away if you remove *every* occurence of "overflow" except for the one in "#soorttekstlayer". You have so many things overlapping I think you are actually seeing the scroll bar for some other div. It's still odd that Mozilla would layer the scrollbars differently with different themes, and end up with the wrong one on top. I think the bug is actually with z-index when using Mac OS aqua scroll bars.
I have created two additional test pages. 1. http://www.eti.uva.nl/ruud_temp/mozilla2.html All overflow attributes removed: Mozilla displays layers and scrollbars correctly in all themes. 2. http://www.eti.uva.nl/ruud_temp/mozilla3.html Overflow set to auto: Mozilla displays correctly in all themes. Conclusion: css coding error! Or not? 1. Themes in Mozilla behave differently. 2. Although inappropriate discussing this here: the problem is that the latest build of Mozilla displays correctly, Netscape 7 and Chimera do not. I was under the impression that all use the same engine. However, Chimera 0.6 does not display any scrollbars when the overflow is removed or set to auto. The same applies for Netscape 7.
Ruud, can you still reproduce this problem using a current nightly build?
The problem still persists. Here is the page in Classic theme.
Why is overflow:-moz-scrollbars-vertical used rather than the standard overflow:scroll?
Because, as you can see in the other two example pages, Chimera and Netscape were not displaying scrollbars at all. However, we have changed the code a bit. Previously the z-index of the visible layer was increased, now the visibility of the other layers are set to "hidden" and overlfow: "auto" is used.. This results in normal scrollbars in all browsers. Anyway, it's still curious that the themes render the page differently!
So it sounds like the only thing you're still reporting is that overflow-moz-scrollbars-vertical doesn't result in a functioning scrollbar using the Classic theme. Is that the case? Do you care about it?
Comment 9•20 years ago
|
||
Unfortunately, the three test-page URLs mentioned in this bug report no longer exist. (They forward to the site's home page.) Else, I'd see if I could reproduce this one using the latest Mozilla daily build under MacOSX. -- David Lawhon
Reporter | ||
Comment 10•20 years ago
|
||
Probably this is related to http://bugzilla.mozilla.org/show_bug.cgi?id=187435
Comment 11•20 years ago
|
||
(In reply to comment #10) > Probably this is related to http://bugzilla.mozilla.org/show_bug.cgi?id=187435 Perhaps, I think that it is it. But there is no test page...
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•