On Apr 6, 6:27 am, "Jukka K. Korpela" <jkorp...@cs.tut.fi> wrote:

> Well, why didn't you tell that in your first posting, and why do you
> _still_ fail to try to find the right group? CSS has nothing to offer
> you but overflow handling.

Sorry, maybe I should have said this in the first post. However, the
problem (of having enormously long words) could occur in other
contexts. Many editors like VI and MSWord do wrap words longer than
one line, so I thought CSS might have a property you can set on a div
to enable this. Maybe they should add a a property "wrapAt" whose
default value is "space" but can be "all". Right now it's as if there
is a <wbr> after every space, so with "all" there would be a <wbr>
after every character.

But you give me an idea -- maybe I can use "overflow:scroll".


> And why would the URL matter? It's available in the address bar anyway.

No, the address bar will show "http://www.mywebsite.com/errors/
404.jsp", whereas I want to echo what the user typed. This is just to
show them what they typed so that they can see the typo and fix it.
Seems more user friendly to me.


> If you really wish to display it, study the URL specs for "URI in
> context" and some Style Guide for rules on admissible breaks in URLs "in
> context", and implement the strategy server-side (assing <wbr> at
> suitable places and doing something the _prevent_ line breaks after
> hyphens).

Thanks, I'll look into this.