When inserting the teaser break tag in source, XStandard shows a little icon in the text in edit mode, apparently this is a known tag. I know customizing the toolbar is a Pro option, but would it be possible to have this included somehow in the Lite version?
Or does anybody know a nice workaround? Best I can think of is a little help text at the bottom of the node edit block that tells people to copy-paste the tag in the source code, but ideally contributors wouldn't have to go to source.

Comments

henrrrik’s picture

henrrrik commented

I think XStandard only recognizes it as a HTML comment and that's why the icon appears. I guess I could add a little help text if a pro key hasn't been entered. I'll add it to the to-do list.

ar-jan’s picture

ar-jan commented

Hm, double-clicking the html comment icon in XStandards text field pops up an 'edit comment' field. Any other way to trigger this comment field to pop-up? then i'd just have to type 'break' instead of the break-tag ;)
Otherwise a little help text would be nice...

ar-jan’s picture

ar-jan commented
Title: XStandard Lite recognizes <!--break--> tag, possible to somehow include this option as button? » XStandard Lite and the <!--break--> tag

I would like to change the topic to something a bit broader, a general 'support for the Drupal <!--break--> tag' issue.

A little help text is one. (A more visual solution like splitting the body field in a teaser and rest of the text field, like the standard Drupal split at cursor, would be even greater, a more fool proof design for contributors who don't know html code).

Another improvement would be a solution for the following problem: when a break tag is inserted into the source code, and then some editing is done in the edit view, it often happens that the break tag ends up inside a paragraph tag. The body text as a whole is still valid XHTML, but a teaser view has a paragraph opening tag that is not closed, since the teaser is cut of at the break tag. Is it possible to somehow implement a correction 'filter' that makes sure the break tag is always in between a </p> and a <p> tag?

ar-jan’s picture

ar-jan commented
Title: XStandard Lite and the <!--break--> tag » XStandard (Lite) and the break tag

correct the title

henrrrik’s picture

henrrrik commented

Splitting the textarea like Drupal does by default would be great, but I don't believe it is possible since XStandard is a browser plug-in and I can't change anything about it once it has been loaded into the page. This also prevents disabling the editor by clicking a button like with FCKeditor and TinyMCE.

It's possible to write a filter that searches for <!--break--> tags nested inside HTML elements and moves them. I'll look into it when I have some spare time.

henrrrik’s picture

henrrrik commented
Assigned: Unassigned » henrrrik
Status: Active » Postponed