Bolding in Show Summaries


LadyShelley wrote 8 years ago: 1

This is bolded

This is italics

Tested and worked in show summary as well.

I'm using Firefox version 53.0

tnt wrote 8 years ago: 1

Hm, awkward. For me it's working on the home laptop, but failing on the office workstation, at least it was today. Both computers are Mac and I'm using Chrome. I'll check more tomorrow at the office, maybe I'll find, what's causing it.


MTQueenie wrote 8 years ago: 1

Weird, it's not working for me either all of the sudden. I'm on Windows and using Chrome, worked fine yesterday.

tnt wrote 8 years ago: 1

Ha!

I've just updated Chrome to the latest version (58.0.3029.81) and it stopped working.

I cannot change style in the first line of text at all, no matter how long it is. On the other lines I can change style only on the whole line, not the separate words.

WilliamWade wrote 8 years ago: 1

tnt wrote:
Ha!
I've just updated Chrome to the latest version (58.0.3029.81) and it stopped working.
I cannot change style in the first line of text at all, no matter how long it is. On the other lines I can change style only on the whole line, not the separate words.

Okay. So it's not just me. I've updated to the latest version of Chrome as well. Same as you.


david wrote 8 years ago: 1

Very odd! Nothing changed on our end, so it must be the Chrome update that broke it. That's quite unfortunate, let's hope they'll fix it soon.

As I said earlier in the thread I've been searching for a decent replacement for the text editor for a long time, but none of the alternatives out there are great either. So I can't offer a quick fix myself except for recommending a switch to Firefox.

tnt wrote 8 years ago: 1

david wrote:
Very odd! Nothing changed on our end, so it must be the Chrome update that broke it. That's quite unfortunate, let's hope they'll fix it soon.
As I said earlier in the thread I've been searching for a decent replacement for the text editor for a long time, but none of the alternatives out there are great either. So I can't offer a quick fix myself except for recommending a switch to Firefox.

It's definitely something in Chrome, because the problem appeared only after update. Something with rendering I suppose.

Safari is working fine.

Maybe it's possible to add some kind if simple text editor with tags support? Not visual I mean, kind of like source editor. As a temporal measure, until you find the replacement.


gazza911 wrote 8 years ago: 1

tnt wrote:
It's definitely something in Chrome, because the problem appeared only after update. Something with rendering I suppose.
Safari is working fine.
Maybe it's possible to add some kind if simple text editor with tags support? Not visual I mean, kind of like source editor. As a temporal measure, until you find the replacement.

2 things:

1. Does it occur using the keyboard shortcuts (Ctrl + B) then typing or by pressing the buttons or both?

2. Are they any error logs that appear in the Developer Console (F12)

(I currently keep my Chrome on an earlier version)

tnt wrote 8 years ago: 1

gazza911 wrote:
2 things:
1. Does it occur using the keyboard shortcuts (Ctrl + B) then typing or by pressing the buttons or both?
2. Are they any error logs that appear in the Developer Console (F12)
(I currently keep my Chrome on an earlier version)

1. both
2. no

I have a suspicion, that the style is changing, but Chrome is failing to render it properly.


gazza911 wrote 8 years ago: 1

tnt wrote:
I have a suspicion, that the style is changing, but Chrome is failing to render it properly.

If you do want to see the actual HTML that will be sent you can enter the following into the developer console (F12)

$(".redactor-editor").next().show();

Paste it in then press enter - The bit in bold should show as a strong tag.

tnt wrote 8 years ago: 1

gazza911 wrote:
If you do want to see the actual HTML that will be sent you can enter the following into the developer console (F12)
$("#comment-create").show();
The bit in bold should show as a strong tag.

No, it's not there. Only a paragraph <p> tag.


gazza911 wrote 8 years ago: 1

Looks to be how the browser is handling:

document.execCommand('strikethrough');

Comparison after command

As you can see, the strike tag is added successfully in the older version, but it is incorrect in the newer versions, hence why it fails.

Try 30 days of free premium.