376274 - Next-Gen Composer: Lock out formatting tools other than CSS styles

Status: NEW

(SeaMonkey :: Composer, enhancement)

Description

[Bryce Mozilla Nesbitt]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20061107 SUSE/1.1.1-0.1 SeaMonkey/1.1.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20061107 SUSE/1.1.1-0.1 SeaMonkey/1.1.1

I'd like to have a composer mode which support only structure level formatting tools (e.g. "list", "h1", "body text", "address", "acronym").

I love the composer application.  I find it to be the most usable simple web page editor out there, never mind that it's free.  But when I give it to the marketing department, they always pervert the CCS styles.

One solution is a composer mode that ONLY allows applying CCS styles.  For example if my stylesheet is:

.legal {color: #646464; font-size: 10px; line-height: 11px; }
h2 {font-size: 13px; line-height: 15px; font-weight: bold; color: #578E00;}
h3 {font-size: 12px; line-height: 14px; font-weight: bold; color: #578E00;}
ul,li {list-style: disc inside url(specialbullet.gif); }

Then the composer "paragraph format" pulldown would have only five named styles that could be applied to the document.  The controls for color, font, etc would be ghosted out.

Abiword has a <abiword template="false" styles="locked"> feature that does just this.

---------------------------------------------------------

As a step toward this, it would be great to have an "apply CCS style" feature.  You could select some text, and surround it with <span class="legal">XXXXXX</span.


Reproducible: Always

Steps to Reproduce:
Hand someone the composer.
Actual Results:  
A mix of structure formatting (e.g. H1) and explicit formatting (e.g. "font +1").

Expected Results:  
A consistent document.

Comment 1

[Tony Mechelynck [:tonymec]]

I suspect that a mode which would disallow "deprecated" tags would stand a better chance of getting implemented, but that would probably not be what the reporter wants, since something like <font size="+1">...</font>, which is deprecated, might be replaced something like by <span style="font-size: 120%">...</span> which isn't.

Comment 2

[Bryce Mozilla Nesbitt]

So disallow style="", but make it very easy to apply a style class that's already defined (e.g. <h1 class="mainhead"></h1>.

Comment 3

[Tony Mechelynck [:tonymec]]

Enhancement-level bugs should be Trunk.

Comment 4

[Phoenix]

Looks like valid rfe, if developers don't think otherwise