Last modified: 2014-02-25 00:14:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T63399, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61399 - Built-in iOS text styling doesn't work in VE
Built-in iOS text styling doesn't work in VE
Status: RESOLVED WONTFIX
Product: MobileFrontend
Classification: Unclassified
alpha (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-14 23:05 UTC by Juliusz Gonera
Modified: 2014-02-25 00:14 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Built-in iOS text styling (236.16 KB, image/jpeg)
2014-02-14 23:05 UTC, Juliusz Gonera
Details

Description Juliusz Gonera 2014-02-14 23:05:46 UTC
Created attachment 14597 [details]
Built-in iOS text styling

If you open VE and select text, you can click on the B/I icon which shows three styling options (see screenshot). The styling is applied in the editor but is not saved later (in fact, you need to change one more thing, e.g. add a character somewhere to be able to save).

We should probably somehow disable those buttons if possible. This might be more of a VE bug than mobile.
Comment 1 Bingle 2014-02-18 18:34:12 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1707
Comment 2 Juliusz Gonera 2014-02-25 00:14:01 UTC
After an initial investigation it seems to be impossible to hide text styling controls in iOS context menus without hiding everything (which we won't do because of copy/cut/paste buttons).

I talked to the VE team and they say that the bug is on their side. In the worst case, VE should detect a change triggered by using those controls and either cancel it or update its data model (see bug 61884).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links