| • Mattflaschen-WMF | |
| Mar 27 2015, 6:59 PM |
| F157762: Screen_Shot_2015-04-27_at_9.27.35_AM.png | |
| Apr 27 2015, 4:38 PM |
This is designed to allow typing an @ sign despite the sequence shortcut (with the current patch, you have to copy/paste from elsewhere).
When you type @, it will open. Then, if you escape without typing a username, an @ sign will be added to the VisualEditor document.
See also: T94109: Click outside to close doesn't always work as intended for mention inspector
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Improve user experience when using '@' sequence trigger for mentions | mediawiki/extensions/Flow | master | +42 -12 |
Change 205100 had a related patch set uploaded (by Esanders):
Improve user experience when using '@' sequence trigger for mentions
Change 205100 merged by jenkins-bot:
Improve user experience when using '@' sequence trigger for mentions
Does not look that it is done in current betalabs env.
if you escape without typing a username, an @ sign will be added to the VisualEditor document.
Returning the bug back to In Development
@Etonkovidova, unfortunately, Beta Labs is stalled (see T92871: Parsoid patches don't update Beta Cluster automatically -- only deploy repo patches seem to update that code). It's not getting new patches.
Works in Chrome.
FF 36 does not look good.
Works in Chrome.
FF 36 does not look good.
- Typing @ will open the mention inspector at the upper left corner dis
- and the mention inspector becomes very sticky - cannot get irid of it until the page is updated.
I can't reproduce this locally.
Are there any errors in the browser console when this happens?
Looks like I can reproduce this in beta labs after all, I get Error: Offset could not be translated to a DOM element and offset: 7.
I've now gotten Chrome to give me this error too. Assigning to Ed as this is a bug in VE.
This is merged now, so the Firefox issue (which also occurred in Chrome if you typed @ directly after another mention) should be fixed.