Note: There are a few cases of duplicates in user autocompletion which are being worked on.

[RFE] allow stylesheet creation/manipulation : CSS in Composer step 3

RESOLVED FIXED in mozilla1.0.1

Status

SeaMonkey
Composer
P3
enhancement
RESOLVED FIXED
18 years ago
13 years ago

People

(Reporter: CodeMachine, Assigned: glazou)

Tracking

Trunk
mozilla1.0.1

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(3 attachments)

(Reporter)

Description

18 years ago
This is a request for a "simple CSS editor".  It wouldn't expose the language,
but rather would generate a stylesheet.

The base of this should be the settings in the NN4 Appearance Tab.  The ability
to ignore BLINKs would be nice too.  =)

The CSS editor could be used to edit or create a new user style sheet, or edit a
CSS file similarly to the editor.

Of course, it's difficult to take an arbitrary CSS stylesheet and convert it
into these prefs, so it might be save-only for files, and you'd need to keep
user stylesheets in both forms.
(Reporter)

Comment 1

18 years ago
Bug #17534 is about a full CSS editor.

Not sure whether this bug is a Browser or Editor thing, BTW.

Updated

18 years ago
Assignee: leger → pierre
Component: Browser-General → Style System
QA Contact: leger → chrisd

Comment 2

18 years ago
Putting on correct component and setting QA contact.

matty@box.net.au - instead of using the Browser-General component so often,
please check out:
http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
when writing a bug and try to get on the correct radar on initial submit.
This could speed up things a bit for ya.  :-)

Updated

18 years ago
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → LATER

Comment 3

18 years ago
Funny... It seems to me that Bug 17534 is a simple css editor (just some syntax
checking and highlighting) while this bug is in fact a request for a full-fledged
css editor (GUI only, no exposure of the code). I agree with you: "it would be
nice if..." but I'm not sure we want to commit to that business even more.
Closing as Later.
(Reporter)

Comment 4

18 years ago
Consider this request as just a bunch of controls, like you have with the NN4
appearance page (eg default page colours).  There might be a few checkboxes like
"don't allow blink".

I don't know how you could do CSS without exposing the code, but however you do,
this isn't a request for it.

Comment 5

18 years ago
The current plan is to let users add "!important" rules in ua.css (like minimum
font sizes for visually impaired people, specific color sets for color-blinds
or... no blink for epileptics). The problem is to figure out what other settings
could be of interest for enough people to justify a GUI.

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 6

18 years ago
Verified LATER

Comment 7

16 years ago
reopening my LATER'd bugs

Comment 8

16 years ago
really reopening...
Status: VERIFIED → REOPENED
Resolution: LATER → ---

Comment 9

16 years ago
Reassigned to Daniel (fyi only)
Assignee: pierre → glazman
Status: REOPENED → NEW
(Assignee)

Comment 10

16 years ago
This is a RFE for the 3rd step in the CSSization of Composer [1].
Its purpose is creation and manipulation of stylesheets in Composer.
This is not too hard to do but implies a lot (really a lot) of UI design and
work.

[1] http://www.mozilla.org/editor/adding-css-to-editor.html

Accepting Bug :-) (does not mean I'm going to work on it right now tho)

See also bug 77705 (step 2) and bug 16255 (step 4).
Status: NEW → ASSIGNED
Component: Style System → Editor: Composer
Summary: Simple Stylesheet Editor → [RFE] allow stylesheet creation/manipulation : CSS in Composer step 3

Comment 11

16 years ago
We don't need anything fancy until we implement bug 6782 "UI for alternate and 
user stylesheets".
(Assignee)

Comment 12

16 years ago
*** Bug 34837 has been marked as a duplicate of this bug. ***
(Assignee)

Updated

16 years ago
Depends on: 34849
(Assignee)

Comment 13

16 years ago
milstone bulk change
Target Milestone: --- → mozilla1.0.1
(Assignee)

Comment 14

16 years ago
Created attachment 78540 [details]
work-in-progress screenshot 1


Here is a first screenshot of my Stylesheet management dialog. I am working on
it
on my personal time, so no ETA. Everything there is subject to changes and even

complete rewriting, so don't focus on string or design choices.
(Assignee)

Comment 15

16 years ago
Created attachment 79435 [details] [diff] [review]
work-in-progress code #1

Comment 16

16 years ago
Changing QA contact
QA Contact: chrisd → madhur
(Assignee)

Comment 17

16 years ago
Created attachment 79809 [details]
work-in-progress screenshot 2
(Assignee)

Comment 18

16 years ago
Related products of interest :

   Westciv's StyleMaster     http://www.westciv.com/style_master/index.html
   Westciv's LayoutMaster    http://www.westciv.com/layout_master/index.html
(Assignee)

Comment 19

16 years ago
CaScadeS project requested on Mozdev ; XPI will be available from there
as soon as I get the account.
(Assignee)

Comment 20

16 years ago
Added an expert mode toggle in the dialog :

  - in expert mode, all creation buttons (sheet, rule, @media, ...) are enabled
    depending on the selection in the sheets/rules tree. The user cannot create
    a rule w/o having a sheet first. All kind of selectors are available

  - in "not expert" mode, only the rule button is enabled. Creating a rule inserts
    it in the last embedded sheet in the document, and even creates a sheet if
    needed. User cannot create media-based stylesheet nor other complex css stuff.
    CSS rule creation offers to create "named styled rules" (class attribute)
    or "element-based rules" (type element selector)
(Assignee)

Comment 21

15 years ago
all work visible at http://cascades.mozdev.org/ starting from now
(Assignee)

Comment 22

15 years ago
fixed by CaScadeS landing in mozilla/extensions/editor/cascades (was bug 161663)
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago15 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.