Closed
Bug 373314
Opened 18 years ago
Closed 17 years ago
strange transparent areas in firefox caused by xul
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: guninski, Unassigned)
Details
Attachments
(1 file)
(deleted),
application/vnd.mozilla.xul+xml
|
Details |
strange transparent areas in firefox caused by xul
wi=window.open();
window.fullScreen=true;
alert("reload");
wi.close();
when opened as the first tab (no other tabs present) and then just reloaded
causes the following weird effect:
part of what should be firefox window is transparent and if
the content is desktop its items are visible and clickable.
part of the xul is visible or semi visible (font with
transparent background).
the bug is in both trunk and 2.0 on linux, macosx seems
safe. trunk may need several reloads.
this allows tricking the user into dragging desktop items in
the location bar and probably in other areas.
not sure if this is exploitable, but consider it quite
anomalous.
Reporter | ||
Comment 1•18 years ago
|
||
strange blinking behaviour in icewm, works fine in gnome & kde
Comment 2•17 years ago
|
||
Is this still an issue in current trunk build?
Reporter | ||
Comment 3•17 years ago
|
||
this seems fix on current trunk.
though the testcase gives strange errors:
Security Error: Content at chrome://global/content/bindings/preferences.xml may not load data from http://localhost:8080/trans2.xul.
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMXULElement.boxObject]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://browser/content/tabbrowser.xml :: _notifyBackgroundTab :: line 2693" data: no]
###!!! ASSERTION: Adding child where we already have a child? This will likely misbehave: 'Error', file /opt/joro/firefox-cvs/mozilla/docshell/shistory/src/nsSHEntry.cpp, line 595
Reporter | ||
Comment 4•17 years ago
|
||
i mean this seems fixED on current trunk
Comment 5•17 years ago
|
||
I'll mark fixed. 1.8.x release drivers should figure out if they can, or want to pick up the fix.
Status: NEW → RESOLVED
Closed: 17 years ago
Flags: wanted1.8.1.x?
Resolution: --- → FIXED
Updated•12 years ago
|
Group: core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•