All

I'm just creating a new thread based on https://www.elevatesoft.com/forums?action=view&category=ewb&id=ewb_general&page=1&msg=15092 as the subject was misleading and the issue I have now lies in problems with Chrome and time columns

Tim. Did you get my small project to demonstrate my problem with Chrome?

Just to summarise, I have a time diary app that lists event from midnight to midnight with a Time From and Time To field. Time columns in my understanding are not UTC related, however my time columns still seams to change based the users timezone settings. I have not checked the LocalizeDateTimeColumns to be clear.

My biggest issues is that on Chrome the time values are wildly off. Not just Time Zone off but the both minutes and hours are completely wrong. This renders my app not usable on Chrome. My problem is that I have previously recommended all my users to use Chrome

Anyone seen this before?

Tim. Looking forward hearing from you regarding my test project I sent.

Thanks

Eivind

Eivind,

<< Tim. Did you get my small project to demonstrate my problem with Chrome? >>

Yes, but I haven't had a chance to look at it yet.  I'm working all weekend, every weekend, but am having a hard time catching up...

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> working all weekend

Be sure to take some time off. Much as we appreciate your output, we don't want you burning out either. Thanks!

--

Matthew Jones

+1

Den 10-10-2018 kl. 09:58 skrev Matthew Jones:
> Tim Young [Elevate Software] wrote:
>
>> working all weekend
> Be sure to take some time off. Much as we appreciate your output, we don't want you burning out either. Thanks!
>

Yes, but I haven't had a chance to look at it yet.  I'm working all weekend, every weekend, but am having a hard time catching up...

Tim Young
Elevate Software
www.elevatesoft.com

@Tim. Yep, I know that feeling all too good. Too much work sometimes

Matthew,

<< Be sure to take some time off. Much as we appreciate your output, we don't want you burning out either.  >>

Thanks, but most of my time is getting eaten up with support stuff, so it's more that than over-working on the development front.  When I get the time to do development, I'm good to go.

Sam and I need to sit down and get the support situation ironed out at some point, but that's been a bit of a chicken-and-egg situation, also.  It's kind of a free-for-all right now, and I know that we're getting killed on the time costs that aren't being charged for.  In addition, I just put updating our internal software/servers off for too long, and now I'm paying the price this year.  But, slowly but surely, I'm working through the backlog and moving the ball forward.  Unfortunately, I keep letting my frustrations spill out here in some of my replies, and I need to give that a rest.

Tim Young
Elevate Software
www.elevatesoft.com

Eivind,

<< @Tim. Yep, I know that feeling all too good. Too much work sometimes >>

Yeah, it simultaneously feels great to be busy, but also oppressive because it never ends.

At any rate, like Moses with the parting of the Red Sea, my workload lightened up yesterday as I was finally able to get a big issue with another product off my to-do list.  So, I took a look at the project that you sent me, and I am seeing the same time values in both Edge/Firefox and Chrome.  You're saying that you're seeing different time values for the "raw" times vs. the times constructed from strings, correct ?

As for the sorting of the time values, yes, that is a known issue and I covered that in my previous replies.  I'm hoping to address this in EWB 3 by simply getting rid of localization of date/time values on the server-side, but there are also some significant downsides to doing this for some customers, so I'm still "on the fence".  I might split the difference and just get rid of localization for times and leave the localization in place for date/time and date values.

Tim Young
Elevate Software
www.elevatesoft.com

Eivind,

BTW, I *really* like that dark color palette that you used for your example application.

Tim Young
Elevate Software
www.elevatesoft.com

--------------------- From Tim---------------------------
At any rate, like Moses with the parting of the Red Sea, my workload lightened up yesterday as I was finally able to get a big issue with another product off my to-do list.  So, I took a look at the project that you sent me, and I am seeing the same time values in both Edge/Firefox and Chrome.  You're saying that you're seeing different time values for the "raw" times vs. the times constructed from strings, correct ?
---------------------------------------------------------------------

Tim. The "raw" values from the server are the same. It's how Chrome and Opera displays them that bothers me. Take a look at the attached 4 images. One is from Safari on Mac that is correct. You can see the time diary starts at 00:00 and ends at 00:00. At this point the list is sorted bye the calculated field of type string to overcome the sorting problems. If you look at the other 3 images you can see that the time values on Chrome (Mac and Win 10) and Opera are completely different. The time values does not even resemble the correct values. However, the same data is loaded from the server.

As a side note, I did not have these issues a few months ago and I know I upgraded to the newest version of Chrome lately. Are you seing the exact same time values on Chrome as well. (From 00:00 to 00:00)?. Anyhow, I guess I have to check out some Internet cafes and try other computers as well. Will continue to investigate.

As for the dark theme, thats the result of merging about 5 Delphi VCL themes and picking out the best part of each. Quite happy with the design, but there are a few minor changes I'm still working on.

Ok Tim, more test results here and I think I'm getting closer to narrowing down the problems. It seams to me it's both a matter of the version of Chrome and timezone issues. I have been going crazy on www.browserstack.com with both windows and Mac simulators and there I found the following:

Mac OsHigh Sierra:
- Chrome 66 OK
- Chrome 67 --> UP, NOT OK

- Opera 53 OK
- Opera 54 --> UP, NOT OK

Then I started looking in to timezones and went through different timezones on my computer. Both Mac and Windows. What I found out was that all timezones from UTC to UTC -12 generated good time values (Correct time values). From UTC to UTC +12 generated messed up time values. Please have a play around with browser versions and timezones with my project and see if you can replicate the same I found.

Thanks and best regards

Eivind