User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:126.96.36.199) Gecko/20060111 Firefox/188.8.131.52 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:184.108.40.206) Gecko/20060111 Firefox/220.127.116.11 In the "Disabling XUL by section" by Alex Vincent on April 06, 2006; the textbox for "disableSection.js" is overlaped by the Blogs links "Subscriptions" column on the right. Please view... http://www.flickr.com/photo_zoom.gne?id=124474163&size=o Reproducible: Always Actual Results: http://www.flickr.com/photo_zoom.gne?id=124474163&size=o Expected Results: It should not have been overlaped. http://www.flickr.com/photo_zoom.gne?id=124474163&size=o
Which part of it are you objecting to? I'm pretty sure that the subscriptions column should overlap the textarea, since the subscriptions are position: absolute, and the textarea has a fixed width from cols="80", so the position:absolute wins the z-index fight. The Mac-only "scrollbar has a higher z-index than the textarea itself" seems very wrong, though the only mention I can find of something similar is in bug 294653, which makes it sound like there are lots of bugs on that already.
Severity: trivial → normal
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → Trunk
Created attachment 217532 [details] testcase As you narrow the width of your window, "foo" goes over the top of the textarea, except on the Mac, where it slides in between the scrollbar and the rest of the textarea.
Phil, are you still able to reproduce this in Firefox 3 / on trunk? /me does not own a Mac to test :(
Which, the scrollbar thing? That wasn't what this bug was actually about, but that was fixed ages ago. What this bug was actually about was a layout module peer saying "yep, that testcase is an accurate minimization of the situation, and position:absolute is supposed to come out on top in that case, invalid." I guess that stopped actually happening several years ago, though.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.