Topic: Long words in SMF should use <wbr> (Read 887 times)
No, browsers that don't support degrade very nicely: they act as if was not present. No special char needs to be removed.
However, it's a bitch and a half when the browser doesn't recognize it, because instead of having to find and delete a space when you copy text, you have to find and delete a character that you can't even see.
SMF breaks up long words by inserting a space every 79 characters (it is a space in a with a negative margin). Example: here are 120 'a' characters:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
When copying/pasting the chars, the space is visible at the 80th position, which is very annoying...
Instead, SMF should insert the standardized tag (word break opportunity) already recognized by most browsers. In theory is identical to U+200B (ZERO-WIDTH SPACE) but this is false; for example the current Chrome version on Linux (Version 23.0.1271.97) replaces U+200B with '#' when copying & pasting to a non-UTF8 application, whereas is nicely invisible...
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
When copying/pasting the chars, the space is visible at the 80th position, which is very annoying...
Instead, SMF should insert the standardized
Jump to: