161487 - Create component for Editor : CSS Editor

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

Asa, it has been suggested during last Editor meeting to put my CSS editor,
available from http://cascades.mozdev.org/, in the trunk, available by default
in Composer.

Aside of the technical issues, we think that we need a new component in Browser
for that. We already have "Editor : Core" and "Editor : Composer" and we would
like to have "Editor : CSS Editor". The default owner for this component could
be myself.

Comment 1

[Asa Dotzler [:asa]]

Has this code been checked into the mozilla tree?

Comment 2

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

asa: not yet because I don't know if there is a process I should follow. Do I
just create extensions/cascades and check my code in, outside of the build, or
is there a more formal process ?

Comment 3

[timeless]

i think you get approval from [e-mail]'s proxy (leaf)

but for this bug we'd like a QA Contact and a description :-)

Comment 4

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

> i think you get approval from [e-mail]'s proxy (leaf)

Ok. Asa, do you confirm ? I am ready to donate my code to Mozilla.org but
would like to do the things cleanly.

> but for this bug we'd like a QA Contact and a description :-)

Description : For bugs in CaScadeS, the CSS editor in Composer. Appropriate bugs
include those related to the manipulation of CSS stylesheets in Composer through
the "CSS editor" menu entry but do not include those related to the manipulation
of inline styles directly applied to elements in the STYLE attribute.

QA contact : asking sujay if he can be the QA contact ; stay tuned.

Comment 5

[Asa Dotzler [:asa]]

Daniel, creating new directories requires staff (really Brendan's) approval.
I'll bring this up at our Wednesday meeting.

Comment 6

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

> Daniel, creating new directories requires staff (really Brendan's) approval.
> I'll bring this up at our Wednesday meeting.

Asa : sure, I was not going to create a dir w/o staff approval. I sent a mail about
it to staff@m.o last friday.

Just to be very explicit : cascades does not add any single
line of c++ to Mozilla. It's purely chrome, can stand 100% in extensions/cascades
and is of course XPIable.

Comment 7

[Asa Dotzler [:asa]]

code is in the tree. component is in bugzilla. Daniel, can you get the OK from
Sujay and I'll update the QA contact (it's you for now). Leaving this bug open
and morphing it to "update QA contact" because I'm lazy. 

Comment 8

[timeless]

Can you capitalize the 'e' in CSS _E_ditor? (occurs twice)
This follows the 'prevailing style':
/extensions/editor/cascades/resources/locale/en-US/cascadesOverlay.dtd, line 40
-- <!ENTITY cascadesMenuItem.label "CSS Editor">
/extensions/editor/cascades/readme.html, line 109 -- under Tools&gt;CSS Editor.<br>

Also given that my nightly mozilla doesn't seem to have CaScadeS, should 'in' be
changed to 'for'?: CSS editor _in_ Composer

notes: component created.

Sujay: will you be the QA contact?

Comment 9

[Hixie (not reading bugmail)]

->me

Comment 10

[Hixie (not reading bugmail)]

No response from Sujay. I've updated the spelling in the description. Marking
FIXED. Please file a new bug if there are other issues.

Comment 11

[timeless]

vrfy fixed