TinyMCE: Limit Tag Use

1 Reasons to Abandon Feature

Killing, Alexander [alex], 25 Apr 2018: The TinyMCE editor has been introduced in 2006 into ILIAS. The responsible developer left a few years ago and since then the component is not under a real maintainership (no first/second maintianer, I listed myself as "implicit" maintainer to have anyone listed at all) and it never got any decent funding. The use of the component for developers, its configuration in the administration and the user experience is sub-standard.

I suggest to remove the support for the following tags to reduce the number of formats and the complexity of the underlying HTML. I goal could be to have a smaller subset of HTML that maps e.g. to a subset of markdown syntax.

Abandonded tags:
"hr",
"cite",
"dd",
"div",
"dl",
"dt",
"object",
"param",
"span",
"strike",
"ruby",
"rbc",
"rtc",
"rb",
"rt",
"rp"

Questionable:
"table",
"td",
"tr"

Resulting supported set:
"a"
"blockquote",
"br",
"code",
"em",
"h1",
"h2",
"h3",
"h4",
"h5",
"h6",
"img",
"li",
"ol",
"p",
"pre",
"strong",
"sub",
"sup",
"u",
"ul"

In my view table editing in TinyMCE is still coming with a bad user experience. As it also adds lot of complexity to the underlying HTML I would prefer not to support it anymore.

2 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

3 Contact

• Author of the Request: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

4 Funding

Removing the feature from the ILIAS code base might need funding. If you are interest in funding this request, please add your name and institution to this list.

• ...

5 Discussion

Use the following discussion section to express your objections against this request or your consent to get rid of this feature.

6 Implementation

{The maintainer has to give a description of the final implementation and possible consequences for existing installations.}

Approval

Approved at {date} by {user}.