-
_From @GoogleCodeExporter on April 18, 2015 5:51_
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not reco…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
* **I'm submitting a ... **
- [X ] bug report
- [ ] ~~feature request~~
- [ ] support / question
## *Brief Description*
When entering dates in the filter for thanksgi…
-
### Problem to solve
[Most countries](https://en.wikipedia.org/wiki/Week) consider Monday the start of the week:
![wikipedia](https://upload.wikimedia.org/wikipedia/commons/e/e2/First_Day_of…