Apr 25 2017
May I ask why you are acting like you are still an active member of the team?
The behavior you are describing means the user can smash the return key very early, and will entirely miss the preview that is shown after the input was parsed and formatted.
I don't think it's broken per se. In any case, supporting saving of unparsed values (i.e. ad-hoc parsing) is quite some new feature which would require a lot of work.
Apr 24 2017
@Lydia_Pintscher Why is this an “Epic”? The task's title is way too generic for the given description and what is discussed on http://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2013/06#minimizing_Item.27s_UI all of which could be done without too much effort but which would arguably require a little more thought and discussion. Way too exaggerated to call these minor design changes a “Redesign Item UI”.
Marked as resolved as pointed out by TheDJ.
@Lydia_Pintscher According to Thiemo, “it should definitely be fixed”. There will always be some non-critical issues for long periods of time in almost any serious software project and that's fine.
Apr 23 2017
@Lydia_Pintscher Please do not just “Decline” a task without an explanation why. This is irritating.
Feb 5 2017
(optional) deduplication of libraries
Aug 22 2016
@Lydia_Pintscher Please elaborate on why this got closed as declined. @Snaterlicious' glossary seems like a good initial effort to this task. So why not build on top of this and commit to cleaning up the mess we've gotten into by not drawing a clear line between Wikidata and the Wikibase software it is based on?
Aug 2 2015
About the mixin, you are right there, my mistake.
Jul 31 2015
To elaborate: The bad thing here is that register() and unregister() have different function signatures than the ones stated in the "super class", resulting in a violation of the class' (or interface's) contract.