[wp-trac] [WordPress Trac] #28206: Include 'source anchor' in wpLink quicktags modal for improved ui/ux

WordPress Trac noreply at wordpress.org
Sun Jan 11 22:58:15 UTC 2015


#28206: Include 'source anchor' in wpLink quicktags modal for improved ui/ux
-------------------------+------------------------------
 Reporter:  netweb       |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  3.9
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui
-------------------------+------------------------------
Changes (by netweb):

 * keywords:  reporter-feedback =>


Comment:

 Replying to [comment:6 avryl]:
 > So there is no visual editor available? It sounds like you're giving
 them the wrong tool. If they don't have any HTML skills, why give them an
 editor that will generate HTML?
 Correct, the Visual Editor is not enabled by default, it can be enabled
 via a filter though, the issue of using the Visual Editor vs the Text
 Editor are both historical (forum users want a simple BBCode type
 experience) and complicated due to these two issues:
 * Switching between the Visual Editor and Text Editor the code/post/text
 changes (This hasn't been closely looked at since switching to TinyMCE
 v4.x, but is planned)
 * Allowing users to replace the Visual Editor with their own editor of
 choice

 bbPress 1.x is NOT a WordPress plugin and uses its own editor, adding a
 link on WordPress.org support only prompts for the link, no title or link
 text, it works and it's simple
 https://wordpress.org/support/forum/alphabeta#postform

 As bbPress 2.x IS a WordPress plugin we rely on WordPress' text editor
 "out of the box" so to speak.

 Replying to [comment:6 avryl]:
 > Would renaming it to "Title attribute" help?
 I don't think renaming `Title` to `Title attribute` would help, this would
 still be clear as mud for those with no HTML knowledge.

 Replying to [comment:6 avryl]:
 > Or would just disabling it if no text is selected be better?
 At the moment I think that would be better, though still not ideal, some
 conditional scripting foo would help but I agree in that I don't think
 this addresses the main issue.

 ''p.s. I have no such JavaScript foo skills, so that is one reason I've
 not looked at this as an option ;)''

--
Ticket URL: <https://core.trac.wordpress.org/ticket/28206#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list