Frontend shall ALWAYS use server's time zone

[teosarca]

Is this a bug or feature request?

FR backend task: https://github.com/metasfresh/metasfresh-webui-api/issues/1064

What is the current behavior?

Frontend is using browser's timezone

Which are the steps to reproduce?

What is the expected or desired behavior?

Frontend shall use server's time zone.

Server's timezone is provided by /rest/api/userSession endpoint. e.g.

{
....
"timeZone": "+02:00",
...
}

[teosarca]

@siemiatj playing around i got OOM

[teosarca]

update: i think it was some buggy chrome plugin i've used to change my timezone.

[metas-dh]

Results of IT1 tested in mf15

pls see IT for https://github.com/metasfresh/metasfresh-webui-api/issues/1064#issuecomment-432213324: NOK

from teo's test, browser in EEST, server in CET:

[metas-rc]

I found the same problem in Date filters.

[metas-rc]

Case 2)

• Note the value and valueTo have different time zones. Probably from the daylight saving:

[siemiatj]

Can you record a video or give info what's happening, what data did you send and what did you get from the server ? The initial problem was that dates had different TZ locally and on the server. Server is +1 and I switched to Romanian TZ (+2). Before my changes time would change here to be an hour earlier. Now it's not happening anymore. So if it's not fixed I need to have a test case, expected outcome and so on :

http://recordit.co/hjmJAIW3m2

[metas-rc]

Hi. I recorded a video with what happens on my side. The problem seems to be that the frotend first sends the date with timezone +00:00 and only afterwards it's changed to +01:00 ( this is the server time zone). The results is that my filter Nov 1 -> Dec 1 turns into Nov 1 -> Dec 2

http://recordit.co/KdzMzSXyop

[siemiatj]

Might be related to #2202

[siemiatj]

Related to #2219