mozapps/preferences/preferences.css not found

RESOLVED FIXED in seamonkey2.0

Status

defect
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: mnyromyr, Assigned: mnyromyr)

Tracking

({fixed-seamonkey2.0})

Bug Flags:
wanted-seamonkey2.0 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

On opening preferences in my trunk debug build, I get 

Chrome file doesn't exist: /XXX/mozilla/dist/bin/chrome/toolkit/content/mozapps/preferences/preferences.css

at the command line.
Some file is up to date. The filefield binding was moved somewhere else. Did you clobber your dist?
Oops. We need to remove these lines:
http://mxr.mozilla.org/comm-central/source/suite/common/pref/preferences.xul#42
http://mxr.mozilla.org/comm-central/source/suite/common/pref/pref-download.xul#41

The filefield binding is now in xul.css (and has been for ages).
Assignee: nobody → mnyromyr
Status: NEW → ASSIGNED
Attachment #396591 - Flags: superreview?(neil)
Attachment #396591 - Flags: review?(neil)
Comment on attachment 396591 [details] [diff] [review]
kill mozapps preferences.css includes

> <?xml-stylesheet href="chrome://communicator/skin/" type="text/css"?>
>-<?xml-stylesheet href="chrome://mozapps/content/preferences/preferences.css"?>
Oops, overlays don't need stylesheets that preferences.xul already includes...
Attachment #396591 - Flags: superreview?(neil)
Attachment #396591 - Flags: superreview+
Attachment #396591 - Flags: review?(neil)
Attachment #396591 - Flags: review+
(In reply to comment #4)
> (From update of attachment 396591 [details] [diff] [review])
> > <?xml-stylesheet href="chrome://communicator/skin/" type="text/css"?>
> >-<?xml-stylesheet href="chrome://mozapps/content/preferences/preferences.css"?>
> Oops, overlays don't need stylesheets that preferences.xul already includes...
Filed bug 513895.
Pushed as <http://hg.mozilla.org/comm-central/rev/11ee32afb19b>.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: wanted-seamonkey2.0+
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0
You need to log in before you can comment on or make changes to this bug.