Closed
Bug 195681
Opened 22 years ago
Closed 14 years ago
Visibility check fails for BeOS - DrawTile is called for really obscured areas
Categories
(Core Graveyard :: GFX: BeOS, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: sergei_d, Assigned: sergei_d)
References
()
Details
DrawTile is not so effective on BeOS currently (IMHO this is at all not best
idea to render background in OffscreenImage->ToScreen way), and if it is called
permanently triggered by all repaint events, it is absolutely catastrofic for
such sites as www.nbc.com.
Second good illustration - if to drag some object over big scrollbar knob -
Mozilla still causes scrollbar background pattern re-rendering, inspite dragging
occurs over invisible (obscured by knob) background area.
Though, in general, repaint area (and so Tile to repaint) are detected correctly.
Comment 1•22 years ago
|
||
.
Assignee: other → arougthopher
Component: Layout → GFX: BeOS
QA Contact: ian → timeless
Assignee | ||
Comment 2•22 years ago
|
||
Boris, currently i'm unsure that this bug should be assigned to BeOS port
mantainer. Until someone helps me to understand mechniscs of this visibility
check. As far as i understand, layout engine handles information about z-order,
parent-child relations and regions itself, outside port-code (widget or gfx)
Sergei, as you have a better understanding of the gfx code for BeOS, I am going
to change the assignment of this bug to you. If that's a problem, set it back
to me.
Assignee: arougthopher → sergei_d
Assignee | ||
Comment 5•20 years ago
|
||
No, it didn't.
I think it is rather meta-bug.
Partly related to generic gecko-problems:
http://wiki.mozilla.org/index.php/Gecko:Invalidation_Handling
http://wiki.mozilla.org/index.php/Gecko:Frame_Painting
Updated•16 years ago
|
Product: Core → Core Graveyard
Comment 6•14 years ago
|
||
We don't support BeOS any more.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Comment 7•14 years ago
|
||
In the graveyard, code referred to doesn't exist to be fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•