Closed
Bug 258406
Opened 20 years ago
Closed 18 years ago
Setting zIndex with javascript causes select elements to lose viewed (scrolled) position
Categories
(Core :: Web Painting, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: guvnikov, Assigned: roc)
References
Details
Attachments
(1 file)
(deleted),
application/xhtml+xml
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
With a select element that has been scrolled down, when a parent element has its
zIndex modified the select loses the position it had been scrolled to and
returns to the top.
When using moveable elements on my page it becomes bothersome.
Attempting to capture doubleclick on the select (to act based on choice) and
capturing mousedown/click on the containing element (to move it to top, ala
windowing) makes it impossible to doubleclick select anything in the select
element without an inelegant (and function limiting) event.stopPropagation()
Reproducible: Always
Steps to Reproduce:
1. Create a div element that contains a select element.
2. Scroll down on the select element.
3. Modify the zIndex of the div.
Actual Results:
Select loses its scrolling position.
Expected Results:
Select should maintain its position and not reset the scrolling.
Added attachment.
Reporter | ||
Comment 1•20 years ago
|
||
Comment 2•20 years ago
|
||
The scroll position is stored in the frame, which is destroyed and rebuilt when
z-index changes because view creation may be needed....
This will probably be fixed by bug 249102
Depends on: 249102
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Updated•18 years ago
|
Attachment #158177 -
Attachment mime type: text/html → text/xhtml+xml
Updated•18 years ago
|
Attachment #158177 -
Attachment mime type: text/xhtml+xml → application/xhtml+xml
Comment 4•18 years ago
|
||
Testcase seems to work fine... marking WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•