Page MenuHomePhabricator

"Leave feedback" link has confusing scope
Closed, ResolvedPublic0 Story Points

Description

Component: UI

The speech bubble icon and "Leave feedback" link in Visual Editor look like they apply to the page being edited. I was expecting a Talk: tool.

It would be more clear if the text were "Report bug in Visual Editor", but that's annoyingly verbose. Which is sort of the intention here, I assume ;) Normally, this link would get buried in a dropdown menu or something, IMO.

The problem is exacerbated if you are sort of blind and zoom in your browser a lot, because the VE feedback link becomes very prominent once the toolbar is wrapped.

Details

Reference
bz47815

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

bzimport raised the priority of this task from to Low.
bzimport set Reference to bz47815.
bzimport added a subscriber: Unknown Object (MLST).
awight created this task.Apr 29 2013, 5:54 AM

The feedback link isn't a VisualEditor item but part of MediaWiki core. Moving bug appropriately.

Adding many blockers of bug 38638 to the list of "easy" bugs, to mark them as candidates for [[mw:Google Code-in]] tasks (gci2013). If you think this bug is not suitable, remove the keyword.

matmarex renamed this task from [mediawiki.feedback.js] "Leave feedback" link has confusing scope to "Leave feedback" link has confusing scope.Dec 21 2014, 6:30 PM
matmarex updated the task description. (Show Details)
matmarex set Security to None.
matmarex removed a subscriber: Unknown Object (MLST).
matmarex added a subscriber: matmarex.

The link is now neatly tucked inside a dropdown menu. There's no screenshot on this bug, so I can only guess that it wasn't like this before. This probably resolves the issue sufficiently.

Nemo_bis closed this task as Resolved.Dec 26 2014, 4:08 PM
Nemo_bis claimed this task.

Yep, from what I recall of the past and my understanding of the report, the issue looks solved.