Open
Bug 15321
Opened 25 years ago
Updated 2 years ago
Styleless mode
Categories
(SeaMonkey :: Composer, enhancement)
SeaMonkey
Composer
Tracking
(Not tracked)
NEW
Future
People
(Reporter: CodeMachine, Unassigned)
References
Details
(Keywords: helpwanted)
It'd be nice if you could change to a "styleless mode", where all references to
style disappear, both on the toolbar and menu items, except of course stylesheet
stuff.
Reporter | ||
Comment 1•25 years ago
|
||
You should only be able to change to this if there is no HTML style.
For new documents, whether to open in styleless mode if it has no style should
be a preference.
Updated•25 years ago
|
Assignee: buster → cmanske
Target Milestone: M20
Comment 2•25 years ago
|
||
reassign to cmanske for M20
Reporter | ||
Comment 3•25 years ago
|
||
Authoring Tool Accessibility Guidelines Sep 3 99, checkpoint 1.2, referring to
Web Content Accessibility Guidelines 5 May 99, checkpoint 3.3.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 4•25 years ago
|
||
Matty: It would help if you put the URL for the accessibility guidlines here.
Thanks.
Reporter | ||
Comment 5•25 years ago
|
||
See parent tracking bug.
Comment 6•25 years ago
|
||
Matty, can you explain, what you mean with "styleless" more exactly?
Anyway, I would like the basic editor UI not creating any presentational tags,
but some advanced UI (not necessarily a different mode) for stylesheets. (This
means, the editor wouldn't use <b> or <font> anymore.)
Reporter | ||
Comment 7•25 years ago
|
||
Yes, it means that no options are presented to demonstrate things like <B>, <I>,
<FONT>, <CENTER>, etc. Similarly you could not attach inline CSS style to
spans.
Instead you use <DIV>, <SPAN>, <EM>, etc, along with classes and ids.
On second thoughts, you could probably move into styleless mode if there is
style, but it should prompt whether to remove all style, and if it doesn't,
you'd need to access those things through advanced edit or some such thing.
A smart tool for converting <B> to <EM> and so on would be useful too.
Comment 8•25 years ago
|
||
The Authoring Tools Accessibility Guidelines are now a recommendation:
<URL:http://www.w3.org/TR/2000/REC-ATAG10-20000203/atag10-chklist>
Comment 9•25 years ago
|
||
Oops, that was the checklist URI. The guidelines URI is
<URL:http://www.w3.org/TR/ATAG10>!
Updated•25 years ago
|
Target Milestone: M20 → Future
Updated•24 years ago
|
Status: NEW → ASSIGNED
Comment 13•24 years ago
|
||
Taking bug. Hacking on something like this anyway.
Assignee: cmanske → mozilla
Status: ASSIGNED → NEW
Updated•24 years ago
|
Status: NEW → ASSIGNED
Comment 14•24 years ago
|
||
Changing personal priorities. Giving away most of my bugs :-( (reassigning to
default owner).
I will still track these bugs closely. If you need my input, feel free to ask me.
New owner: Please do *not* close these bugs (as WONTFIX or whatever you may
find) unless they are fixed. Rather, reassign to <nobody@mozilla.org>, if you
don't want to work on them.
Assignee: mozilla → beppe
Status: ASSIGNED → NEW
Target Milestone: Future → ---
Comment 15•24 years ago
|
||
moving bug back to future milestone
Status: NEW → ASSIGNED
Priority: P3 → P4
Target Milestone: --- → Future
Updated•18 years ago
|
QA Contact: sujay → editor
Updated•2 years ago
|
Severity: normal → S3
Comment 17•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: daniel → nobody
Comment 18•2 years ago
|
||
Firefox does not need this feature.
Severity: S3 → --
Component: DOM: Editor → Composer
Priority: P4 → --
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•