Make subscript/superscript switchable

[virtimus@…]

I've observed strange behaviour when switching between subscript/superscript (concerns situations when both are switched on). Added this to fcknamedcommand (start of execute function):

if (((this.Name=='Subscript') &&
(!FCK.EditorDocument.queryCommandState('Subscript')))
|| ((this.Name=='Superscript') &&
(!FCK.EditorDocument.queryCommandState('Superscript')))) {
FCK.ExecuteNamedCommand('RemoveFormat');
}

and voila - subscript/superscript works fine ...

---

Moved from SF:
​http://sourceforge.net/tracker/index.php?func=detail&aid=1428321&group_id=75348&atid=543656

[Martin Kou]

Well... actually it is not an error to have such situation. Many will tell you that this is necessary. For example:

x^B₁

The above is ok. Actually there is a limitation in the editor as it is not able to include a subscript inside another subscript!

But ok, we are not proposing a formula editor here... maybe the "switchable" approach is better?! Any thoughts?

I'm moving it to the Features Requests therefore.

---

Moved from SF. Original poster: fredck

[Alfonso Martínez de Lizarrondo]

#5083 has been marked as dup

[Joe Kavanagh]

If the user clicks the subscript button, then the superscript button, while the same text is selected the result is: ^_text. In this scenario can the sub element be removed, and the subscript button deselected.

[Lynne Kues]

This issue has been raised against the editor in our product. The expected user behavior is that subscript/superscript should be mutually exclusive. That is, if I format the text as subscript, then change to superscript, <sub> should be replaced with <sup>, as indicated in the above comment by JoeK.

[Garry Yao]

Can you cite any editor that have sub/sup exclusive?

[Frederico Caldeira Knabben]

I think MS Word is a good example for it.

Considering the limitation precisely described at martinkou's comments, this request is definitely valid.

[Garry Yao]

Replying to fredck:

I think MS Word is a good example for it.

I don't understand, MS Word has exactly inclusive sub/sup.

[Frederico Caldeira Knabben]

Replying to garry.yao:

Replying to fredck:

I think MS Word is a good example for it.

I don't understand, MS Word has exactly inclusive sub/sup.

In my installation (Word 2007), sub and sub are mutually exclusive. In any case, that's just an example, not a rule to be followed.

There are some facts that justify making it mutually exclusive, other than MS Word:

• This is not a formula editor. There are other tools and plugins that provide this feature in the right way.

• The current "feature" is incomplete. If it's possible to have a sub inside a sup, it should be possible to have sub inside another sub, but it's not possible.

• Another issue with the current "feature" is that is should make validations to make it possible to have sub inside sup. Currently, it's possible to have things like the following, which gives a pretty bad output:

x<sup><sub>2</sub></sup>

[Garry Yao]

Well the problem is that current (inclusive) feature is a super set of the proposed feature, as you can always achieve the exclusion via toggle previous one + apply new one.

As you pointed out we're not going to into the formula world it should be a worry of having an incomplete feature.

[Sa'ar Zac Elias]

Proposing a new "toggles" field, that removes the conflicting style if applied on the current selection.

[Frederico Caldeira Knabben]

We don't need a change in the API adding new parameters to pass the toggles thing. We can simply have this in the style definition, much like the overrides entry. In this way we can define styles that get removed by the style application.

Additionally, the "toggles" name is not appropriate, as it refers to a visual action. Better to simply call it "removes", having the same implementation as "overrides".

---

Finally, just to make it reported, after patch, with the following HTML:

<p>x<sup>1234</sup></p>

1. Select "234".
2. Click the "Subscript" button.
3. Without changing the selection, click "Superscript".

Nothing happens... as js error is thrown.

[Nilay Mandal]

I ran into the same situation and found the below workaround for switching the buttons:

$(".cke").find(".cke_buttonsubscript").unbind("click").bind("click", function(e){

if($(this).parents(".cke").find(".cke_buttonsuperscript").hasClass("cke_button_on")) {

$(this).parents(".cke").find(".cke_buttonsuperscript").click();

}

});

$(".cke").find(".cke_buttonsuperscript").unbind("click").bind("click", function(e){

if($(this).parents(".cke").find(".cke_buttonsubscript").hasClass("cke_button_on")) {

$(this).parents(".cke").find(".cke_buttonsubscript").click();

}

});