Closed Bug 316668 Opened 19 years ago Closed 3 years ago

LinkProperties and SpellCheck dialogs are transparent/black

Categories

(SeaMonkey :: Composer, defect)

1.8 Branch
x86
Linux
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: lloyd, Unassigned)

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5

Flock bug #1348
http://bugzilla.flock.com/show_bug.cgi?id=1348


------- Comment #7 From Erwan Loisant 2005-11-11 10:45 [reply] -------

I found the fix.

I don't post it as a patch because the correction is trivial, and because the
problem is in the Mozilla source code.

We should add:
--
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?> 
--
at the beginning of EdLinkProps.xul and EdSpellCheck.xul.
http://lxr.mozilla.org/mozilla/source/editor/ui/dialogs/content/EdListProps.xul
http://lxr.mozilla.org/mozilla/source/editor/ui/dialogs/content/EdSpellCheck.xul

With Firefox 1.0.x it works fine without it, but with Firefox 1.5 any dialog
without this line appear transparent.

We can tell to the MoFo about it, but since the Mozilla Suite is no longer an
official project and Firefox has no editor, I don't know if these files are
still maintained. Both have been modified April, 19 of 2004: almost one year
and a half!



Reproducible: Always

Steps to Reproduce:
confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
Firefox v1.5.x is not supported anymore.

Can you reproduce with Firefox v2.0.0.14 ?
Assignee: composer → nobody
Component: Composer → Editor
Keywords: regression
Product: Mozilla Application Suite → Core
QA Contact: editor
Version: unspecified → 1.8 Branch

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5

Although I don't think this kind of bugs are still reproducible, these files are in comm-central now. So moving to SeaMonkey.

Severity: S4 → --
Status: NEW → UNCONFIRMED
Component: DOM: Editor → Composer
Ever confirmed: false
Priority: P5 → --
Product: Core → SeaMonkey

I think this no longer occurs and did go away with a previous fix in either SeaMonkey or the OS

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.