[wp-trac] [WordPress Trac] #18149: Enhance "Insert/edit link" to predict user's intent (was: Removing "http://" in Insert/edit link causes incorrect URL)

[WordPress Trac]

#18149: Enhance "Insert/edit link" to predict user's intent
-------------------------------+-----------------------
 Reporter:  itsalltech1        |       Owner:  azaozz
     Type:  enhancement        |      Status:  reopened
 Priority:  normal             |   Milestone:  3.3
Component:  UI                 |     Version:  3.1
 Severity:  minor              |  Resolution:
 Keywords:  reporter-feedback  |
-------------------------------+-----------------------
Changes (by WraithKenny):

 * keywords:  reporter-feedback dev-feedback ux-feedback => reporter-
               feedback
 * type:  defect (bug) => enhancement
 * severity:  normal => minor


Comment:

 First, removing "has patch" is fine, as the patch fixed a different bug
 and has nothing to do with your issue. No one put "has-patch" on the
 ticket to persecute you in any way. It merely marked that there was some
 code that fixed some bug. It was only applied once. "Others have noted in
 this ticket" that the fixed bug was a bug, not that your issue itself was
 a bug. The comments above do list some reasons as to why this ticket could
 be considered invalid.

 I've tried to help and figure out your issue, even listing out 3
 possibilities. Please see my list above.

 At the core of your issue is that "`http://`" (or at least "`//`") is
 '''required''' in a very technical way for the actual technology of the
 internet (browsers, web protocol, etc.) to work. It has nothing at all to
 do with WordPress itself. It's absolutely not, in any way, a WordPress
 bug. As far as I can figure, your issue is a enhancement request.

 A possible enhancement to requested is something like the following,
 "Please include something in WordPress that will protect Users from User
 Error" as not including "`http://`" in a link is, in fact, '''User
 Error'''.

 Having said that, '''I've actually been working on a patch''' that would
 enhance the feature to address what I assume is your issue. See my
 proposal above.

 If you reread the comments on this ticket you will see that implementing
 this kind of enhancement is more difficult than it appears. Dealing with
 '''user intent''', as mentioned above repeatedly, is problematic in ways
 you don't seem to appreciate. Usually, it is so problematic that it can't
 be implemented without hurting user experience for everyone else, or it's
 too burdensome to maintain the added code.

 WordPress is built by volunteers. You've asked volunteers to do work
 writing code to help you out, as you haven't submitted any code, or even
 suggested an implementation. I've attempted to do so. What I'm trying to
 say is please use a courteous tone when asking favors.

 I can only spend time working on this during lunch breaks and after work
 as I'm only a volunteer.

 After you respond, please remove the "reporter feedback" tag. If I or
 someone else gets a working patch, I'll reapply the UI or UX feedback and
 Dev feedback tags as appropriate.

 Please also note: Chrome doesn't need the "http://" specifically because
 it doesn't have to guess user intent: URLs are always external in that
 case.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18149#comment:28>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software