Closed
Bug 387988
Opened 18 years ago
Closed 18 years ago
UpdateTranslucentWindow Bug
Categories
(Core :: Widget: Win32, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 385888
People
(Reporter: xfsunoles, Assigned: xfsunoles)
References
Details
Attachments
(1 file, 1 obsolete file)
3.15 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007071213 Firefox/3.0a7pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007071213 Firefox/3.0a7pre
1) There is a bug that is in the UpdateTranslucentWindow functions. It has needConversion = PR_FALSE; in the Cairo builds. if needConversion is false then ::DeleteDC(hMemoryDC); wouldn't executed. I have removed needConversion since it is an useless check.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Assignee | ||
Comment 1•18 years ago
|
||
Attachment #272126 -
Flags: review?(roc)
Component: General → Widget: Win32
Product: Firefox → Core
QA Contact: general → win32
Version: unspecified → Trunk
You shouldn't be deleting hMemoryDC since it's actually stored in mMemoryDC and might be used again ... right?
Assignee | ||
Comment 3•18 years ago
|
||
(In reply to comment #2)
> You shouldn't be deleting hMemoryDC since it's actually stored in mMemoryDC and
> might be used again ... right?
>
right. your want to deleting mMemoryDC then?
As far as I can tell, the widget does not own mMemoryDC when MOZ_CAIRO_GFX is defined. It's just set to mMemoryDC = mTranslucentSurface->GetDC(), which does not transfer ownership.
Probably it would be simpler if we remove mMemoryDC altogether and just use mTranslucentSurface->GetDC() whenever we need to get it.
Updated•18 years ago
|
Assignee: nobody → xfsunoles
Updated•18 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Updated•18 years ago
|
Attachment #272126 -
Attachment is obsolete: true
Attachment #272126 -
Flags: review?(roc)
Assignee | ||
Comment 5•18 years ago
|
||
Assignee | ||
Comment 6•18 years ago
|
||
Is this bug is duplicate of 385888?
Assignee | ||
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•