Closed
Bug 120603
Opened 23 years ago
Closed 16 years ago
URL field should be intuitively clickable
Categories
(Bugzilla :: User Interface, defect, P3)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.2
People
(Reporter: coffeebreaks, Assigned: guy.pyrzak)
References
()
Details
(Whiteboard: [blocker will fix])
could it be possible so that one can click somewhere that points to the value of the URL field? I am tired of copy/paste. or did I miss someting? If one implement that using a link (e.g. a "go" on the right side of the text box), one has to think that the user can modify the URL field, thus not having the same URL in the textbox and in the link.
Comment 1•23 years ago
|
||
It already works that way. If there is a link present inside the field, you'll notice that the field title "URL:" is hyperlinked. Clicking on it will go to the link in the field. I'm going to leave this open however, because it's definitely not intuitive. Everywhere else Bugzilla linkifies a field title, clicking on it gets you a description of that field. Thus I would expect, when clicking on the URL field title to get a description of what the field is for. If I already know what it's for, I wouldn't ever click there if I didn't realize it was the url from the field. Maybe it should be "URL (<a href="blah">click to visit</a>):"
Summary: [RFE URL field should be clickable → [RFE] URL field should be intuitively clickable
Reporter | ||
Comment 2•23 years ago
|
||
Same for me. I was so sure that the link on the field title "URL:" was pointing to the field description as it does with the others fields that I didn't bare trying to click on it. That's why I opened the bug.
Updated•22 years ago
|
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
Comment 3•22 years ago
|
||
"URL" link is not working properly, look at bug 152030
Comment 4•22 years ago
|
||
No, the url link is working correctly - you're missing the http://. bugzilla helper needs to be updated, and tehres a separate bug on that.
Comment 5•21 years ago
|
||
The User Interface component now belongs to Gerv. Reassigning all UNCONFIRMED and NEW (but not ASSIGNED) bugs currently owned by Myk (the previous component owner) to Gerv.
Assignee: myk → gerv
Comment 6•21 years ago
|
||
Reassigning back to Myk. That stuff about Gerv taking over the User Interface component turned out to be short-lived. Please pardon our confusion, and I'm very sorry about the spam.
Assignee: gerv → myk
Updated•21 years ago
|
Summary: [RFE] URL field should be intuitively clickable → URL field should be intuitively clickable
Comment 7•20 years ago
|
||
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 8•20 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Updated•18 years ago
|
Assignee: myk → ui
Comment 9•18 years ago
|
||
justdave in comment #1 > It already works that way. If there is a link present inside the field, you'll > notice that the field title "URL:" is hyperlinked. Clicking on it will go to > the link in the field. holy toledo! I can get 50 cents for every URL I copied in the past 2 years? > *I'm going to leave this open however, because it's definitely not intuitive.* > Everywhere else Bugzilla linkifies a field title, clicking on it gets you a > description of that field. Thus I would expect, when clicking on the URL field > title to get a description of what the field is for. If I already know what > it's for, I wouldn't ever click there if I didn't realize it was the url from > the field. > > Maybe it should be "URL (<a href="blah">click to visit</a>):" 2 ideas: * URL string be followed by "(visit)", ala the "(edit)" indicators on the new UI. * add a small icon/widget that indicates a clickable, external link, ala wiki style. Hidden and nonstandard UI both bad, so IMO "URL" should change to a description like everything else and changing bug severity. (may Gerv be merciful)
Severity: enhancement → minor
Comment 11•18 years ago
|
||
might want to keep bug 86978** in mind when devising the solution to this. **could URLs be separated by space to achieve multiple URLs, and avoid changing a lot of logic associated with URL fields?
Comment 12•18 years ago
|
||
adding justdave's dependency from bug 365312 (should bugzilla warn if the dupee bug has dependencies that will be lost - a whine like "dependencies marked in bug xyz will not be transferred to bug zyx"? I only accidentally noticed the dep, and might have missed it like Frederic did )
Blocks: bmo-regressions-0812
Comment 13•18 years ago
|
||
From dup bug 365312 - when the user does not have permissions to edit the URL (or is not logged in), the URL itself (which is displayed as text) should be linkified, in addition to the "URL" field header.
Updated•18 years ago
|
Target Milestone: --- → Bugzilla 3.0
Version: unspecified → 2.23.3
Comment 14•17 years ago
|
||
dup this also to bug 372966?
Comment 15•17 years ago
|
||
Yeah, that makes sense.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Comment 16•17 years ago
|
||
May be fixed by bug 372966, but in no case a dupe. Especially because I want it fixed in 3.0.x.
Status: RESOLVED → REOPENED
Depends on: bz-url-extension
Resolution: DUPLICATE → ---
Whiteboard: [blocker will fix]
Updated•17 years ago
|
Status: REOPENED → NEW
Comment 17•17 years ago
|
||
I don't think any aspect of this bug could be considered a "regression". Gerv
No longer blocks: bmo-regressions-0812
Updated•17 years ago
|
No longer depends on: bz-url-extension
Whiteboard: [blocker will fix]
Updated•17 years ago
|
Updated•17 years ago
|
Comment 18•17 years ago
|
||
I don't see how this is a bug-fix, and thus worthy of being in Bugzilla 3.0.
Comment 19•16 years ago
|
||
Fixed in Bugzilla 3.1.3 as part of bug 374020. Now that we already released the 3rd minor update on the 3.0 branch, I don't think we need to fix the UI there.
Assignee: ui → guy.pyrzak
Depends on: 374020
Whiteboard: [blocker will fix]
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago → 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•