Ralf Becker f2c4ccd1b0 fixing the fix again: removing check from client side
We can not use "(?<![.\s])", used to check that name-part does not end in
a dot or white-space. The expression is valid in recent Chrome, but fails
eg. in Safari 11.0 or node.js 4.8.3 and therefore grunt uglify!
Server-side will fail in that case because it uses the full regexp.
2018-02-05 17:02:14 +01:00
..
2017-01-31 08:29:00 -07:00
2017-10-10 10:16:08 -06:00
2017-04-06 18:17:47 +02:00