Closed
Bug 207244
Opened 21 years ago
Closed 14 years ago
[RFE] Make a DataSource for font list
Categories
(SeaMonkey :: General, enhancement)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: kenz.gelsoft, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4b) Gecko/20030526 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4b) Gecko/20030526 Mozilla Firebird/0.6 It is very nice to implement a datasource for font list. Making a datasource for font list, which allows us to use RDF-Template for slow font prefs panel now implemented while-looped JavaScript code. It might simplifies and speeds font prefs, and we can create new widgets using font list more easily. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Comment 1•21 years ago
|
||
Confirming. This may need to go to another component.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•20 years ago
|
||
Throwing this one up into the air. This for sure doesn't belong into RDF. It smells like GFX, but it sounds like a really bad idea to make gfx depend on rdf. Not sure if "Layout: Fonts and Text" is any closer.
Assignee: rjc → general
Component: RDF → Browser-General
QA Contact: general
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 3•15 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 4•14 years ago
|
||
I'm resolving this as WONTFIX since mozilla is moving away from RDF as fast as possible.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•