BR tags no longer working in textile
|Resolution:||Wont fix||Affected version:|
I have lots of <br> or <br /> tags in my wiki pages, which are now rendered as text. From the docs I don't see another way to force a break. I wasn't paying very close attention but I assume this was changed in r1216. Could we add this to the list of respected HTML tags? Better yet, could we make that list configurable?
#2 Updated by Rocco Stanzione about 10 years ago
Yeah carriage returns will do line breaks, but like other whitespace consecutive ones aren't respected. Where I'm using the br tags is mostly after wiki tables, where there's an unattractive lack of whitespace between the table and the, say, h2 that comes after it. So, I really only need it for vertical whitespace, not just line breaks. I'll do an example here...
And this is a header¶
There are three carriage returns between the table and the header, and I don't seem to have a way to add actual whitespace between them.
#6 Updated by Morbus Iff almost 10 years ago
- Status changed from Closed to Reopened
Reopening. This killed my wiki.
I have complex HTML needs for a wiki (such as a global Navigation box that appears in the header of every page, and includes <div> formatting) and also go back and forth between a local HTML document and the wiki. I need the ability to include raw HTML in the wiki and have it work as expected. I've now got a 100 page (private) wiki which is horrifically broken due to the escaping :(
Perhaps we could get some sort of <raw> or <html> tag? Textile is not everyone's savior.
#12 Updated by Eric Voisard about 9 years ago
+1: I see many reasons why consecutive line breaks should be respected: readability, page layout, respect to copy&paste structure of text files such as logs, traces, etc... well, all pertain to readability in fact...
Maybe convenience as well: we should expect people updating wikis not all being web developers but MS Word and the like users: with the tools they are used to, when they press <return> several times, it puts space between their lines of text. It's basic and it's the most straightforward way to adjust page layout.
When they (well me too!) do the same in Redmine's wiki editor, I think they expect the same behavior, especially since they can enter blank lines in the editor...
Besides this, thanks to Redmine's Team for the very nice software
#17 Updated by Jean-Philippe Lang about 8 years ago
- Status changed from Reopened to Closed
- Resolution changed from Fixed to Wont fix
+1: I see many reasons why consecutive line breaks should be respected: readability, page layout, respect to copy&paste structure of text files such as logs, traces, etc
Using pre tags is great for logs or stack traces.