Item6810: WYSIWYG monospace button fails in ''s

Type 'abc' into a WYSIWYG box. Select abc (but not the quotes). Click Aa (monospace). Save.

abc isn't monspace, but if you go to raw mode, you'll see '<span>abc</span>' (Yes, you see the single quotes.)

Demonstrated on http://develop.twiki.org/~twiki4/cgi-bin/view/Sandbox/TestTopic6 (and more important places :-()

Had to explain to the technical - much less non-technical user.

P.S. I'm not getting e-mail notification of changes to topics on the bugs web where I'm the reporter...

-- TWiki:Main/TimotheLitt - 2011-09-15

Hmm, this might be a browser specific issue. Just tested using FF 6.0 on OS-X and it works as expected, e.g. abc is enclosed in equal signs.

On your PS: Bug tracking is done on develop.twiki.net. We have not enabled e-mail notification on this server.

-- TWiki:Main.PeterThoeny - 2011-09-21

I'm not imagining this.

Still fails for me. Saw your attempt in my Sandbox topic. It doesn't look to me like you followed the directions.

Type singlequote abc singlequote, where singlequote means the character ' (octal 047), and there are no spaces between the quotes and the abc between them.

Select the abc, but not the quotes. Click monospace. It will look like it worked. Now click Save. The font changes to default.

If you do a raw view, you'll see '<span>abc</span>' - one would expect the <span> to have a style="font:monospace;" parameter, but it doesnt.

Interestingly, if you edit the topic with wysiwyg, the span disappears, the text remains - but not with the correct font.

I'm using Windoze 7, IE 8

-- TimotheLitt - 2011-09-21

And if I click "notifications" on this web (which I got to from report a bug from codev), it sends me to a topic that says "This topic is automatically generated by a script running on the server. The script analyses all the 'WaitingFor' and 'ReportedBy' fields in reports and generates this WebNotify. " So I expected to get notified.

-- TWiki:Main.TimotheLitt - 2011-09-21

Also, verified that Firefox 6.0.2 and Safari 5.1 (windoze) exhibit the misbehavior.

As does Chrome 14.0.835.186 m.

Tried Opera 11.51 - that won't go into WYSIWYG mode. I guess that's another bug.

• 20110921_1318_38.swf: Demo of this bug

-- TWiki:Main.TimotheLitt - 2011-09-21

Yes, my bad, I did not add the single quotes. I can confirm this now using FF 6.0 on OS-X. Is a HTML => TML conversion issue.

-- TWiki:Main.PeterThoeny - 2011-09-21

This bug still persists after the latest WysiwygPlugin update.

-- TWiki:Main.PeterThoeny - 2013-09-28