Ticket #1178 (closed enhancement: fixed)

Opened 14 years ago

Last modified 10 years ago

Improving the Text Widget in the HTML render format

Reported by: madarche Owned by: madarche
Priority: P2 Milestone: CPS 3.4.9
Component: CPSSchemas Version: TRUNK
Severity: normal Keywords: html accessibility


This ticket is to discuss how to to improve the  Text Widget in the HTML render format.

Note that the Text Widget can contain text in different formats. In this ticket we are only discussing the HTML format.

Here are the following modifications that could be done for the HTML render format:

  • By default embed the HTML WYSIWYG editor, do not use a popup anymore.

Rationale: The HTML source would not be displayed by default in the edit mode, but rather the rendered HTML text. Modifying the HTML text would not require another action from the user (opening the popup).

This was not possible to have multiple HTML embedded editors with the old Epoz that CPS was using. But with FCKeditor (cf. #502) and TinyMCE (cf. #1160) this is now possible (and for the record even with the latest version of Epoz).

  • Add an "expand" button to have a big size popup window for easier edition with long texts.
  • Remove the button to switch form one format to another (from HTML format to Text format, etc.).

Rationale: Who needs this anymore? This functionality was maybe there for accessibility but there are other ways to deal with the accessibility of the Text Widget.

  • Take care to provide a textarea equivalent for browsers without JavaScript? support (accessibility).
  • Give the possibility to modify the HTML source directly to:
  • possibly use HTML constructs unknown to the HTML editor
  • give access to edition for unsupported browsers that have JavaScript? support (for example Konqueror)

This could be done in a popup that uses very simple 100% supported-everywhere JavaScript?.

This should be a widget option "edit_source" since in some cases editing through the HTML editor is a checking step.

  • Provide an option to pass the HTML editor some specific options (mainly size)

Change History

comment:1 Changed 14 years ago by madarche

  • Status changed from new to assigned
  • Milestone changed from unspecified to CPS 3.4.1

comment:2 Changed 13 years ago by sfermigier

  • Milestone changed from CPS 3.4.1 to CPS 3.4.2

comment:3 Changed 13 years ago by madarche

This bug could almost be closed since [49008] adds the possibility to have an embedded HTML editor window in the text widget and [49235] makes the rich text editor position a selection property which can easily be extended.

comment:4 Changed 10 years ago by gracinet

Do we close or not ?

comment:5 Changed 10 years ago by madarche

  • Status changed from assigned to closed
  • Resolution set to fixed
  • Milestone changed from CPS 3.5.2 to CPS 3.4.9

Yes this can be considered as fixed.

Note: See TracTickets for help on using tickets.