Opened 4 years ago
Closed 2 years ago
#1485639 closed Bugs (wontfix)
workaround is needed for Opera reflow bug when using two nested elements with position:absolute
| Reported by: | tensor | Owned by: | |
|---|---|---|---|
| Priority: | 8 | Milestone: | 0.6-beta |
| Component: | User Interface | Version: | git-master |
| Severity: | minor | Keywords: | |
| Cc: | suporte@… |
Description
I am an Opera advocate and use it for my every day work. There is a subtle reflow bug in Opera. If the window is resized, sizes of folder list and message list (or preview pane) are not resized accordingly. This bug is has been known for quite some time and has not been fixed in Opera.
See http://www.quirksmode.org/bugreports/archives/2006/02/Opera_absolutefixed_Nested_Positioning.html and http://archivist.incutio.com/viewlist/css-discuss/52336
I have prepared a stripped down example which demonstrates the bug. This example includes a JavaScript? workaround, to see the bug, remove the onresize attribute from the body tag. My workaround is is a first attempt and thus is very rough. It does not work properly when using preview pane, because it forces preview iframe to reload its contents. I also noticed that if I select different folder in the folder list, its size changes to a correct one. I just could not figure out which part of the selection related code triggers a reflow.
Attachments (1)
Change History (3)
Changed 4 years ago by tensor
comment:1 Changed 4 years ago by netbit
- Cc suporte@… added
- Milestone changed from 0.3-stable to later
- Version changed from 0.2-beta to svn-trunk
Thank you by reporting it and the example file.
Issue confirmed with Opera 10.0 beta and 9.64, but It's too specific. I can reproduce it here just by resizing the window through the top or bottom edges (north-resize / south-resize). I cannot reproduce this issue if window is resized by MAXIMIZE button or by another edges (se-resize / sw-resize / w-resize / e-resize).
Have you reported this bug to Opera team?
My vote is for don't add complexity to RC code (that uses more browser/machine resources) due to this very specific and small bug.
comment:2 Changed 2 years ago by alec
- Milestone changed from later to 0.6-beta
- Resolution set to wontfix
- Status changed from new to closed
It looks fixed in Opera 11.10.

stripped down example file