Status

()

enhancement
P4
normal
20 years ago
12 years ago

People

(Reporter: CodeMachine, Assigned: glazou)

Tracking

({helpwanted})

Trunk
Future
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

20 years ago
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

20 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

20 years ago
Assignee: buster → cmanske
Target Milestone: M20

Comment 2

20 years ago
reassign to cmanske for M20
Reporter

Updated

20 years ago
Blocks: 16397
Reporter

Comment 3

20 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

20 years ago
Status: NEW → ASSIGNED

Comment 4

20 years ago
Matty: It would help if you put the URL for the accessibility guidlines here.
Thanks.
Reporter

Comment 5

20 years ago
See parent tracking bug.
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

20 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.
The Authoring Tools Accessibility Guidelines are now a recommendation:

<URL:http://www.w3.org/TR/2000/REC-ATAG10-20000203/atag10-chklist>
Oops, that was the checklist URI. The guidelines URI is 
<URL:http://www.w3.org/TR/ATAG10>!

Comment 10

19 years ago
moving to future milestone
Assignee: cmanske → beppe
Status: ASSIGNED → NEW

Updated

19 years ago
Target Milestone: M20 → Future

Comment 11

19 years ago
moving back to previous owner
Assignee: beppe → cmanske

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 12

19 years ago
added helpwanted
Keywords: helpwanted
Taking bug. Hacking on something like this anyway.
Assignee: cmanske → mozilla
Status: ASSIGNED → NEW

Updated

19 years ago
Status: NEW → ASSIGNED
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

19 years ago
moving bug back to future milestone
Status: NEW → ASSIGNED
Priority: P3 → P4
Target Milestone: --- → Future

Comment 16

18 years ago
-->glazman
Assignee: beppe → glazman
Status: ASSIGNED → NEW
QA Contact: sujay → editor
You need to log in before you can comment on or make changes to this bug.