Many unrecognised characters everywhere. See screenshots. Happens with any encoding (I tested utf8, iso8859-1, iso8859-7).

CommentFileSizeAuthor
fontproblem.jpg86.03 KBnsk

Comments

TDobes’s picture

Title: unrecognised characters » wbr tag problems with konqueror

This appears to be a problem with Konqueror attempting to render the <wbr /> tag as some sort of non-existant character. The boxes on the screenshot appear everywhere a wbr tag is used.

I do not experience this problem in Firefox, Opera, or IE6.

nsk’s picture

perhaps this tag shouldn't be used since it creates problems for a number of users.

junyor’s picture

Agreed, especially as it's invalid XHTML.

nsk’s picture

Please remove wbr tags. They create problems on Konqueror and I am unable to read the words where wbr are present. wbr tags are not part of any W3C standard.

nsk’s picture

Title: wbr tag problems with konqueror » Please remove the non-standard wbr tags
moshe weitzman’s picture

Title: Please remove the non-standard wbr tags » wbr tag problems with konqueror
Priority: Critical » Normal

it is part of the HTML4 standard. nsk - you linked to a different tag.

junyor’s picture

Would you please link to WBR's location in the spec.? I can't find it.

moshe weitzman’s picture

hmm. now i can't find it either. i guess it isn't part of an official standard. so yeah, lets strike it. see http://www.blooberry.com/indexdot/html/tagpages/w/wbr.htm

Steven’s picture

Most likely this is caused by the following CSS rule in the stylesheet:
wbr:after { content: "\00200B" }

I guess Konqueror doesn't know how to deal with it. Pity. Until I find a method of word breaking which works on as many common browsers as wbr + this, I'm inclined to leave it in. WBR is not in HTML because the Unicode (non-)joiner characters are supposed to be used instead, except support for them is appaling.

What happens if you install a Unicode font which includes the character properly? Or doesn't KDE/Konqueror support font substitution?

tagman23’s picture

Project: Drupal.org site moderators »
Component: web site » usability

There may be a better way to hack this tag. Consider the following code:

wbr {
display: inline-block;
width: 0;
overflow: hidden;
}

You might also try this tag in the beginning of your document, before the html tag:

<!ELEMENT wbr EMPTY>

That should make the tag validate.

cosmicdreams’s picture

Status: Active » Postponed (maintainer needs more info)

Looks like this issue got into the user experience queue and died. I'm confused as to where it belongs. What do others think?

Anonymous’s picture

Project: » Drupal core
Version: » 7.x-dev

The user experience project is closing so this issue is being moved to the usability component under the Drupal project

sun.core’s picture

Project: Drupal core » Drupal.org site moderators
Version: 7.x-dev »
Component: usability » Site organization
Status: Postponed (maintainer needs more info) » Active

Completely wrong queue.

vm’s picture

Project: Drupal.org site moderators » Drupal.org infrastructure
Component: Site organization » Drupal.org theme
gerhard killesreiter’s picture

Status: Active » Closed (won't fix)

nobody cares for a browser with less than 0.5% of page requests. Also, bluebeach will be retired soonish.

Project: Drupal.org infrastructure » Bluecheese
Component: Drupal.org theme » Miscellaneous