Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ichernev
Copy link
Contributor

One of the things that is broken on Android is "including a trailing UTC in the
input should work", which is a test added a long time ago, that used the fact
that ISO format matched beginning of string.

So right now this test goes through Date, which is different on regular vs
mobile browser. Also adding UTC at the end doesn't make it parse a UTC date, so
its misleading to say the least.

I think removing the test makes the most sense in this case. The behavior (of
adding UTC at the end is not documented, so shouldn't break legitimate code).

One of the things that is broken on Android is "including a trailing UTC in the
input should work", which is a test added a long time ago, that used the fact
that ISO format matched beginning of string.

So right now this test goes through Date, which is different on regular vs
mobile browser. Also adding UTC at the end doesn't make it parse a UTC date, so
its misleading to say the least.

I think removing the test makes the most sense in this case. The behavior (of
adding UTC at the end is not documented, so shouldn't break legitimate code).
icambron added a commit that referenced this pull request Oct 14, 2013
@icambron icambron merged commit 5b30f66 into moment:develop Oct 14, 2013
@icambron
Copy link
Contributor

@ichernev Agree on all points. If you want to tack random stuff on the end of a date string, it had better be handled by the Date constructor. If Android doesn't handle a trailing 'UTC', those are the breaks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants