When you are typing text in 'blockquote' formatting, every time you type a space, it indents another level of blockquote, so the text ends up shuffling across the screen!! Don't think that's intentional. (DavidChalmers).
- 16 Aug 2007
Black Knight: It's only a flesh wound!
King Arthur: A flesh wound? I just chopped your arm off!
He's not the messiah, he's a very naughty boy!
I can't find anything wrong.... blockquote works perfectly, AFAICT. Can you provide examples?
The blockquote above is not seen as a blockquote when you edit again. So bad example or new bug
I will try now in IE
Blabla in block
Now out of blockquote
And now saving. When I add spaces some text above is shifting a few pixels in IE6. And when I typed the N in Now I could only see half the N
Change from engancement. If the report it true it is a BUG.
- 28 Aug 2007
Block quote feature is for sure broken. When you enter edit again the editor no longer shows the indented text as indented. You just see the html tags. And some new lines are gone making editing a bad experience that has nothing to do with Wysiwyg.
- 28 Aug 2007
What "blockquote feature" are you referring to? I'm missing something here.....
Indent becomes blockquote
- 29 Aug 2007
OK. blockquote tag is not a recognised TML tag, and there is no TML equivalent for that tag (AFAIK). So when you enter a blockquote section, you are entering a tag that TML does not recognise. When you edit again, the translator does it's best to protect the HTML tags you entered (after all you don't want it to munge other HTML tags such as <form> or <a>, do you?)
Not sure what you expect me to do about that. I could make TML recognise blockquote tags, but is that really what we should be doing? How many HTML tags occupy this grey area between HTML and TML?
- 31 Aug 2007
I made the TML2HTML
more forgiving to tags that the editor ought to be able to handle. The requirement is really to protect tags in the source that the editor can't be expected to handle correctly, such as input, form, object, applet etc. Othe tags, such as >br<, it should be able to deal with. Of course tags embedded in TWiki variable parameters are always protected. There is some risk with this approach
; a TWiki application might, for example, open a tag in one topic and close it in an include. By passing these tags unprotected, then the editor will automatically close the tag, which could end up breaking the application. There is no rational solution to this (except to disallow unbalanced HTMl in topics, which is a bit draconian)