blob: 629e25e61b1c9654caff1a4756cb7f6dcd579f68 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
---
layout: post
title: Version 2.0.1
author: matthew
---
<div class="r" align="right">
<a data-flickr-embed="true" href="https://www.flickr.com/photos/s2art/189574055/" title="drowning"><img src="https://c8.staticflickr.com/1/67/189574055_37e836feaa.jpg" width="500" height="375" alt="drowning"></a><script async src="//embedr.flickr.com/assets/client-code.js" charset="utf-8"></script>
</div>
Today we have released **version 2.0.1** of FixMyStreet, a bugfix release.
The issues fixed are:
* Chrome 55 changes the way it handles mouse/touch events, [unifying them as
pointer events](https://developers.google.com/web/updates/2016/10/pointer-events),
and OpenLayers, the JavaScript mapping library we use, needed patching to
deal with this. Thanks to the Chrome team for helping debug this.
* strftime output (e.g. used to display dates) was sometimes being double
decoded, giving incorrect output in some languages.
* If a category was filtered, it was not being properly carried through to the
new report form.
* The body/area inputs in the admin were being fixed to a too-small height.
Some bugfixes and improvements have also been made to the admin inspector
report view, along with a couple of development improvements – the tests coping
better if run on a network that intercepts NXDOMAINs, and a better way of
showing the git version in the admin config.
|
