Martijn van de Rijdt

> although deviating from the spec may not be desirable for enketo Yes, we should follow the spec. It might be worth starting a conversation on changing the spec though....

yes totally, right!

Spec changed or in the process of being changed pending comments from you! https://github.com/opendatakit/xforms-spec/pull/215

The third issue just does not excite me at all... I expect it to be a big headache. It could be something for a fork perhaps, or for the future...

Yes, we'd use the storage solution of the app, so indexedDb for Enketo Express. Indeed for indexedDb the storage is much larger, and depends on the amount of free storage...

I split this issue. The third point (audit) can now be tracked here: https://github.com/enketo/enketo-core/issues/630

I suggest having a look at the [file picker](https://github.com/enketo/enketo-core/tree/master/src/widget/file) and [draw widget](https://github.com/enketo/enketo-core/tree/master/src/widget/draw) for inspiration. And of course the [generic widget documentation](https://github.com/enketo/enketo-core/blob/master/doc/widgets.md) (link prone to change in near future). Note that...

Hi @p-netm, That's great. I think the first step is to see if the issue is caused by some conversion in enketo-core (or enketo-xpathjs). The way to do that is...

Thanks! That's interesting. Good to know that the model value is consistent at least. So 2 issues: 1. time value displayed in the widget after loading the record is inconsistent...

Oh my... :sweat_smile: Thank you for finding this! Yes, this embarrassing bug should actually be fixed in enketo-xpathjs, so a PR is very welcome after all!