Page MenuHomePhabricator

When you double-click to edit MediaWiki should highlight the appropriate word in the edit textbox
Closed, DeclinedPublic

Description

Author: jasonspiro4

Description:
MediaWiki lets users with double-click editing enabled edit pages just by
double-clicking anywhere on the page. But I would appreciate it if, when you
double-click to edit, the editing textbox automatically highlighted the word you
double-clicked.

See also related idea: bug 9367.


Version: unspecified
Severity: enhancement

Details

Reference
bz9366

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 9:37 PM
bzimport set Reference to bz9366.
bzimport added a subscriber: Unknown Object (MLST).

This would require wrapping every word in some kind of <span> with attached
information about where in the source text it occurred. Even if we could figure
out how to do that in the parser, it would increase our bandwidth requirements
several times, costing us tens of thousands of dollars per month.

So... probably not right now. :)

  • Bug 9367 has been marked as a duplicate of this bug. ***

jasonspiro4 wrote:

I'm not 100% sure but it seems you don't have use DIVs. A Google search for:

javascript "clicked word"

finds a variety of relevant results. So, I am taking the liberty of reopening this.

Anyway, even if you choose not to provide word-level granularity, you could
still provide paragraph-level granularity; it probably wouldn't be as hard.

ayg wrote:

The basic problem is we currently have no idea what parts of the rendered page correspond to what
parts of the markup. Some parts may be templates, for instance, or any number of other things.
Plausibly future improvements in Web technology or how pages are stored or something might make
this possible, so I'll call it LATER, but this is not practical at the moment. If you disagree,
please provide a patch to the code that will implement this. Do not reopen this bug otherwise.

jasonspiro4 wrote:

(In reply to comment #4)

The basic problem is we currently have no idea what parts of the rendered page

correspond to what

parts of the markup. Some parts may be templates, for instance, or any number

of other things.
...

If the feature I am requesting only worked 95% of the time, that would still be
wonderful.

(Then, later on, if the parser were made to output <span class="template"> tags
as [[meta:WYSIWYG editor]] describes, the feature could be improved and made to
work all the time.

Why is a 95% solution unacceptable?

(In reply to comment #5)

Why is a 95% solution unacceptable?

Because people expect 100% & will file bug reports about the remaining 5%. Moving from deprecated "LATER" to "WONTFIX" resolution as per comments.

jasonspiro4 wrote:

I thank you all for your feedback on this bug.

I've just filed an easier-to-implement alternative:

Bug 42701: "When I double-click to edit, please scroll the edit area to the section I double-clicked".