SaaS Application and timezones - javascript

I have a multi tenant asp.net application. In it each user can set their timezone. However often users log in from browsers where the timezone is different to the preference they have set in my asp.net solution. I want to know, the best practise, should I always force the user to change his computer's timezone to that of his preference in my asp.net application
OR
Should I not bother and let him be in whichever timezone he is in? Any advice on the best practise or convention on how the big sites such as salesforce and others operate will be very helpful.
Tx

IMHO, you can save user preferences like timezone and show in the UI. If the user has no preference, use the UI culture to format the data for display in the UI.
Always store date times in db as UTC format and show in the UI based on the configuration or the current locale.
The JavaScript datetime formats are different from the C# formatting.
Please refer
https://msdn.microsoft.com/en-us/library/ff743760(v=vs.94).aspx
And, http://googleweblight.com/?lite_url=https://stackoverflow.com/questions/22096571/explanation-for-timespan-differences-between-c-sharp-and-javascript&ei=30ovNWzN&lc=en-IN&s=1&m=918&host=www.google.co.in&ts=1485879489&sig=AF9NedmhETXDK0ppwa-fSly3Hmy58wdNaw
HTH

Related

What is the most straightforward way to reformat all dates on my website?

I'm building a WordPress based site and the plugin that delivers the core-functionality doesn't allow changing the date format via the translation files.
All dates are giving out in an American format ("03-24-2017") and I would like to display them in a European format instead ("24.03.2017").
What would be the most straightforward and efficient way to do this? I googled the problem and found several JS-based libraries, but many of them seem to be to expansive (i.e. they also transform things like temperature, etc.). What I'm looking for is a straightforward solution that just formats the date and doesn't come with too much other technical hangover.
The straight forward way id, Go to Admin Panel, Open Settings, you can check Time Format
Choose Custom and add m.d.Y format.

How to get date formats of client machine for a web application?

In my web application, I need to retrieve the client side date formats (Both Long and Short) and need to add it in the cookie. I will retrieve this value from the cookie from the server side. Am assuming, the only possible way is through JavaScript and but am not able to find any solution for it. Any pointers will be helpful.
Note: I don't need to just display the time in client format. Instead, i need to get the format itself. Am able to handle time zone properly and this is nothing related to time zone.
please see the attached image, for what I am exactly looking for.

How does toLocaleString() get timezone in Javascript

Background Information
I am struggling a little on an SPA dealing with time zones. I am looking to capture the current time when a user clicks a button, along with the time zone according to their machine.
My current attempt is to call currentDate.toLocaleString() (see documentation here) and rely on the time zone it is giving me. I've refined that by using 'en' and 'short' arguments, which provide me with a very pretty answer. I am also only supporting chrome (for now anyway) which supports this feature.
Question
My problem is that I need to be able to confirm the degree of accuracy of this call. Which means I would like to know HOW this information is being derived. For example, is it derived from a guess table based on offset? does it query the OS? is there some other system I don't know?
Details
We have some legal constraints on the dates we're gathering, but legal is pelting me with some quite technical questions about exactly how inaccurate our time zone can be, and under exactly which circumstances. The information will eventually be auditable, and it would appear we may be putting some caveats in somewhere based on the answer.
Bonus points if someone can point me in the direction of the code that impliments this feature in chromium so I can confirm for myself (legal doesn't care about that much, but I'm just curious now)
Double Bonus Points if someone can point me in the direction of the most formally accurate way of establishing a string representing time, date, and timezone for the moment of a user interaction in a browser (particularly within the javascript on the browser)
EDIT
I am aware of the browser differences, in broad strokes at least. I am only supporting "chrome" though we don't specify version, we will be run on modern business owned machines, so we can expect somewhat recent versions. That said, if there is a specific effect on the overall accuracy of the time zone portion of the call (the only portion I'm using) I would love to look deeper into that.
We are storing Epoch time (browser) and Epoch time (server) as well as offest (browser) all on top of this piece of information. That said, the only piece of information being displayed to non-technical users is (right now) the time zone, so it has some pressure to be as accurate as possible.
And yes, I checked moment.js and moment timezone, don't get me as close as toLocaleString() (did some hand testing for accuracy)
Final Response
I was aware that this was an extremely challenging problem, but I've learned that it was even more troublesome than I credited it with. Thank you for the information on the limitations faced here, which at the very least will provide our business users with a very clear idea of just how much of a compromise this data would be. Thank you very much for leading me as far from my ignorance as I could get! ^_^
Man, time is hard.
The only thing you can guarantee is that the current time, and the current time zone offset associated with the current time is the one that is in effect on the user's computer - as set by the user.
var d = new Date(); // the current time on the PC running this code
var o = -d.getTimezoneOffset() / 60; // the current UTC offset on the PC running this code
The offset alone does not tell you the full time zone (see "time zone != offset" in the timezone tag wiki), but does tell you how far from UTC the local time was for that particular point in time.
Both of these values are based on settings that the user can usually control on their PC, so from a legal perspective, you cannot trust that they are anything in particular.
The values you can get from toLocaleString are locale-specific, and implementation dependent. In many cases, they are determined via ICU, which in-turn, uses values from CLDR. The time zone itself is always pulled from an OS setting, which may be a TZDB identifier, or a Microsoft Windows time zone setting that goes through CLDR mappings.
If you really want to dig in, you can see the API docs for the TimeZone class in ICU. Chrome likely uses the createDefault function of this class to decide what the time zone is on the machine, and the getDisplayName function of this class to produce the result shown by toLocaleString.
WRT alternative approaches for increased accuracy, there's not much you can do in this area, because ultimately you trust your user to give you accurate information. However, if you have some other piece of data that you can gather accurately (such as GPS position), you can try one of these techniques to resolve the time zone. Keep in mind a clever user might still be able to spoof their location, or you may just have inaccurate location data depending on how it was derived, but it's usually more trustworthy than a setting the user can choose - especially on a mobile device.
"Which means I would like to know HOW this information is being derived. For example, is it derived from a guess table based on offset? does it query the OS? is there some other system I don't know?"
In Short: The user specifies their locale within the browser at install / configure time.
In Long:
Digging around, determining the locale of the user is based on settings built within the browser. Each browser has a list of languages in some preference order that is maintained to satisfy the locality query. These are set at install / configure time. This list of language preferences is used to satisfy locale issues, and is also passed on each HTTP request as a header.
See:
http://norbertlindenberg.com/2012/12/ecmascript-internationalization-api/index.html#Identifiers
Essentially, the user is going to configure the browser with their language (either directly or via the version of the installer they select) so that it is usable to them. The browser keeps this information stored locally, it doesn't need to rely on the OS to keep this information.

Date and time dependant client server web apps

I read some articles regarding web applications which depend on the date and time and geographical position.
I am interested in finding here a few best practices and even solutions for java web applications which client side happens to be on Angular.
I am looking for the best way to store the dates and times in my database so that I can determine their values based on user's location. We have some help here from the Javascript side which can determine the user's timezone.
Any advices, best practices and solution would be great.
I want to know from your experience what is the best way to do this thing because each article I read had a slightly different solution and that small diference caused iasuea later.
You may want to check out Moment.js, and specifically the Timezone add-on if you haven't already... it will take ISO 8601 datetime formatted string by default, the industry standard on any platform.
The Timezone is useful in dealing with timezones and converting between them etc.
This format encodes the UTC time with a timezone part, with high precision.

Can I tell my browser to render a page as if I were in another locale?

I am in the US and have Irish client. I need to ensure that all of the date/times are rendering properly in the European fashion.
I am using JQuery's datepicker and full calendar.
Can anyone help?
I believe you can change the locale on your computer using the Control Panel if you have Windows. Also, refer to http://www.w3.org/International/questions/qa-accept-lang-locales and you will see that a lot of applications use this header among possible other headers to determine a locale.

Categories