Bug #67096
closed
Usage of definition list in RTE
0%
Description
Hello,
I am not sure if this is a RTE bug or a configuration bug.
When I try to add a definition list in RTE, the lists starts the right way with <dl><dt>. After I enter a value in dt and press return to enter a dd-value, the editor replaces the dl tag with a p-tag.
But when I create an empty p-tag by just pressing return and start a definition list after that, the list works like a charm.
Are there others experiencing this issue?
I try it in lastest Chrome and Safari on OS X.
Files
Updated by Riccardo De Contardi over 8 years ago
- Status changed from New to Needs Feedback
- Assignee set to Tim Schreiner
Hi Tim,
I performed a test using TYPO3 6.2.15 and in TYPO3 7.5-dev (latest master), using the attached .ts configuration and completely fresh installations.
Step followed:
1) create a new content element (TEXT)
2) click on the RTE (do not write anything!
3) click on the "Definition list" button
3.1) the following code is added:
<dl><dt> </dt></dl>
4) type something "prova" and hit return
4.1) the code becomes:
<p>prova</p><p></p><dl><dt> </dt></dl>
5) click again on the "Definition list" button
6) type something "prova2" and hit return
6.1) from here the dl/dt works every time I hit return
I also performed a test with the standard RTE configuration, adding only RTE.default.showButtons = * and the results are the same. So it is not a problem about configuration.
I also found another scenario in which the dl/dt works correctly:
1) create a new content element (TEXT)
2) click on the RTE (do not write anything!
3) type something "prova" AND AFTER THAT click on the "Definition list" button
4) in this way the text is converted to the definition list and it immediately starts working correctly.
I think this is the correct way to do things; can you tell me if according to you this solves your problem?
Updated by
Updated by Riccardo De Contardi about 8 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Tim Schreiner)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
You could also join the #typo3-cms channel in Slack if you still need support.
Thank you