-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing issue with timezone since 1.10.2 #1318
Comments
still open in 1.10.3 v1.9.7 |
will fix soon |
any update on this issue? I'm still having this issue but only on android device android chorme 88.0.4324.93 has this issue but not 86.0.4240.198(browserstack) I narrowed the issue down to the timezone function(remove the time zone and the parsing work again). ps. downgrade to 1.9.8 doesn't fix the issue |
IMHO the easiest (the right?) solution is to use the
|
Thanks @BePo65 that workaround is working. But the bug remain :) |
Of course You are right; in the documentation for parse > string it says
And the offset is part of ISO 8601 (see e.g. wikipedia). So we need to find someone who has the time to improve the regex for parsing the ISO_8601 date 😁 |
ISO 8601 date string can have an offset; moment parses this correctly. Issue fixed; tests added / updated.
ISO 8601 date string can have an offset; moment parses this correctly. Issue fixed; tests added / updated.
Hi there - is there a timeframe before this is merged? |
Describe the bug
Running v1.9.8:
Running v1.10.2:
Removing the timezone from the source string and the date is parsed again:
Looks like the regex (#1307) still need improvement I guess?
Expected behavior
Date properly parsed.
Information
The text was updated successfully, but these errors were encountered: