3

I saw this answer over at german.stackexchange.com and thought 'Hey, a typing error! Let's fix it.'

I went into edit mode and saw that the word is already written correctly: 'streichen'.

I am confused. Why doesn't SE show the last 4 characters? I opened the same question in multiple different browsers, all with their newest builds. And only my (old) Opera 12.16 doesn't render it properly.

It took me some minutes to figure out that a soft hyphen (ASCII 173; ­) sits between strei and chen.

Can this somehow be fixed by Stack Exchange?

Improve this question
5
  • 1
    Based on this Opera 12 should be supported...
    – rene
    Mar 7, 2014 at 11:27
  • @rene The answer is a bit outdated but you're still correct, while Windows and OS X are on v20 right now (release schedule similar to Chrome), Linux is still on v12.16
    – Stijn
    Mar 7, 2014 at 11:48
  • A month ago edited and now already outdated! Time flies if you're having fun.
    – rene
    Mar 7, 2014 at 12:14
  • 3
    How is balpha's answer relevant, though? You're seeing that in an answer, not in a comment (which is the only place those auto-insertions occur). That soft hyphen was inserted by the author of that post, or possibly the source he copied it from. Aside from that, this is Opera's problem, not ours. Hiding text after a soft hyphen sounds like a pretty serious bug and past removing all soft hyphens (which isn't going to happen) there's nothing we can do about it.
    – animuson StaffMod
    Mar 7, 2014 at 13:17
  • @animuson I see. I removed the second part regarding balphas answer
    – nixda
    Mar 8, 2014 at 0:32

1 Answer 1

Reset to default
4

Confirmed. (Opera 12.16 on Linux here too.)

This only seems to happen inside code blocks (specifically, elements styled with white-space: pre; inline code with white-space: pre-wrap seems to be fine).

I don't see any real reason to have soft hyphens inside code blocks (except maybe in the mobile view, but the styling is different there anyway), so SE could just strip them out. In fact, adding a client-side fix to SOUP shouldn't be difficult, either.

That said, this really is a bug in Opera, and should be reported.*

Test case:

The long­er words in this text will be trun­cat­ed in Op­era.

These words will not be trun­cat­ed in Op­era.

*) In fact, I've just done that; the bug ID is DSK-388102.

Ps. While waiting for an official fix, I've added a client-side fix for this issue to the Stack Overflow Unofficial Patch v1.10 (which should also have significantly improved Opera compatibility in general). Basically, what my fix does is simply remove any soft hyphens found inside <pre> tags on Opera.

I've also tried to make sure that the removal code gets re-run if any new posts are loaded by AJAX, or when the editor preview is updated. Alas, this latter feature seems to work somewhat unreliably, with the editor hooks sometimes failing to be applied. If anyone can figure out why that might be happening, please let me know! In the mean time, reloading the page seems to usually fix it.

Improve this answer
0

Not the answer you're looking for? Browse other questions tagged .