|
Actually option 2 won't include a CRLF in the copied output - the <wbr> is not an actual <br>, it's a hint to the browser as to where it can break the line. It's equivalent to copying normally wrapped text. The main concern with #2 is that <wbr> is not compliant XHTML.
Make it smaller is probably good. overflow:auto will create a horizontal scrollbar if it needs to which I think looks a bit ugly, but is a possibility. This is really a nasty problem--I wouldn't consider it minor. The horizontal scrollbar adds an extra vertical scrollbar, making editing of long pages, such as we are developing for Sakaibrary, very difficult.
What about putting the URL in a read-only text field? Text fields can be scrolled. Other options are to generate short URLs like Confluence does, or provide a "copy URL" button. Sorry this took so long. I put the URL inside of a fixed width textarea, provided link to select the text and a link to launch URL in a new window.
This has been tested with the default skin, window set at 850px wide, no scrollbar. Gonzalo,
good idea about putting in a textarea, but instead of a user having to click a link to copy the text, what if when a user clicks on the textarea, it automatically selects the contents so they just need to copy it, just a simple onclick="this.select();" attribute in the textarea tag will do it. That would be great. Gonzalo, doesn't look like you're an active watcher on this issue at the moment, so I'm just re-assigning it to you so you'll see Steve's comment above, and consider incorporating it into the fix. Thanks.
Steve,
The reason I added the select() to the link was because it seemed clearer. If the action is on the textarea then we will also need to add a "click on the text to select" no? Hi Gonzalo,
they need to click something anyway, and when a user goes to click the test in the textarea it will all highlight for them (with the onclick="this.select();") so could just save a few clicks. Anyway its not a huge issue so if we could just get a patch to fix the behaviour for now, that would be great. cheers, Steve Gonzalo, this looks great, thanks!
Committed to 2.4.x svn commit -m " Sending content-bundles/types.properties Sending content-tool/tool/src/webapp/vm/resources/sakai_properties.vm Transmitting file data .. Committed revision 49094. This works fine with sakai/trunk on Oracle.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Minor
Long URLs do not wrap, creating horizontal scrollbar in Resources
If this is true, then we cannot use option 1 above as some users will not think of the "copy link: option. We cannot use option 2 either as the copy operation will include $crlf in most os.
A third option is to a) make the font smaller, and b) wrap the URL in a block with overflow:auto. a) will minimize the number of cases where the displayed URL will be wider than the viewport, and b) will allow for copying when it is without forcing the viewport to grow wider.
What do you think?