Page MenuHomePhabricator

an enhancement of the wiki internal links (links to other articles)
Closed, ResolvedPublic

Description

Author: aibras

Description:
i think it it would be much easier for the user and will save the wiki servers some processing time; if the user can get a peek look into the other linked article just by moving the mouse over the link.

sometimes I need to take an idea [the first few lines] about the other article that is linked to my original one; what I usually do is: I open the new link over the current one or in a new tape then I read the first few lines. however, the rest of the article & the embedded media on it usually got downloaded into my system & cost the wiki server some amount of time with no value to anyone at all.

if the users get the choice to either open the article or peek on it, I think many of them will choose to peek on the article.

technically, I believe this enhancement will not require any change in the core app; just a few lines in the interface with a little data retrieval modification to get the peek of the article.

the only drawback of this enhancement is: a) if this change got implemented in the user interface by using java script maybe some of the users will not get the benefit of it. b) if the user peeked into the article then decided to open it, the processing time will be = peek processing + whole page processing; which is will not go with the idea behind this enhancement mostly for the wiki server side .


Version: unspecified
Severity: enhancement

Details

Reference
bz18486

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:31 PM
bzimport set Reference to bz18486.
bzimport added a subscriber: Unknown Object (MLST).

happy.melon.wiki wrote:

This functionality is already available through scripts such as [[WP:POPUPS]]. Strongly disaprove of adding it to core JavaScript, doubly so to core code. Page loading and rendering is definitely not the biggest bottleneck in MediaWiki's performance.

  • This bug has been marked as a duplicate of bug 503 ***