Bug 1328002 - Comments will over the textbox when input a long URL
Summary: Comments will over the textbox when input a long URL
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: develop
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 08:32 UTC by wangdong
Modified: 2016-04-19 22:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-19 22:16:34 UTC


Attachments (Terms of Use)
overstep (70.19 KB, image/png)
2016-04-18 08:32 UTC, wangdong
no flags Details

Description wangdong 2016-04-18 08:32:22 UTC
Created attachment 1148127 [details]
overstep

Description of problem:
When user want add a long URL in comments or input a long comments without white space, it will over the textbox.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Open job page.
2. Add a long URL comments
3.

Actual results:


Expected results:
All comments should in textbox

Additional info:

Comment 1 Roman Joost 2016-04-19 04:58:33 UTC
Hm... perhaps allow scrolling if the comments overflow the containing div? I'm not sure if that's not worse tho. Scrolling vertically is always such a pain, that I'm almost inclined to leave it in case it happens so often that we should do something about it.

Comment 2 Dan Callaghan 2016-04-19 07:23:37 UTC
Scroll bars for horizontal overflow would not be very nice here, since they would appear at the bottom of the pop-up div underneath the comment form.

I am also inclined to WONTFIX this.

Note that since it accepts Markdown, if someone has a very long URL they can turn it into a proper hyperlink using Markdown syntax, as in:

Look at [Beaker search results](http://some/really/long/url)

Comment 3 Roman Joost 2016-04-19 22:16:34 UTC
Dear Dong Wang,

at this point we closing this bug as WONTFIX until it really is a severe issue in production. Thanks for reporting the bug!


Note You need to log in before you can comment on or make changes to this bug.