|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
We have problem with calendar component in FireFox and IE10 browser. But it's work correctly on Chrome. See screenshots: FF, IE: http://joxi.ru/ZrJNPYZI1WBMrjChrome: http://joxi.ru/V2VaPL8h0YoemvProblem appair after we install kb2998527: http://support.microsoft.com/kb/2998527/en-usWhat can we do for fix this problem. Source Code (Sample project): https://drive.google.com/file/d/0B4paYLuQGaaoREg1VmxTN3pNclE/view?usp=sharingThank you.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
We have confirmed this to be a problem. We will post a new build addressing this problem as soon as possible.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
We have posted a new build that should fix this problem. You can download the new build from our download page.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
eo_support wrote:
We have posted a new build that should fix this problem. You can download the new build from our download page.
It's work fine. But we have license troubleshoot (http://joxi.ru/a2XxBZJSyGR62g) we have license for EO.Web version 7.0. licenseId 20081201INTEGRUM What should we do? I read http://www.essentialobjects.com/forum/postst119_License-troubleshooting.aspxbut link http://www.essentialobjects.com/forum/postst50_My-old-license-key-does-not-work-with-the-new-version-what-to-do.aspx doesn't work.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
You will need to purchase a new license in that case. The current version is 2014 (v12) and we offer upgrade discount for the past three versions (2013 - v11, 2012 - v10, 2011 - v9). Your version is too old to qualify any upgrade discount.
In addition to unforeseeable issues like Russia time zone change, the new version also addresses many other issues. The most important ones are newer browser support. Browsers update very quickly these days and it's not uncommon that every new version break a few things. New browsers are also being developed. For example, Google chrome was just starting when your version was released but now it is a very popular browser. The newer version works much better with newer browsers.
When you purchase a license, it automatically includes a one year free upgrade period (that's what the second link which is broken talks about). In your case since your license was purchased many years ago, so this wouldn't apply to you.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 11/13/2014
Posts: 7
|
Thank you, we have purchased a license, but we met with a new defect with DatePicker: On the same host we have delta in one hour beetwen client and server. See screenshots: http://joxi.ru/5md0PYahk5lWm1Source Code (Sample project): https://drive.google.com/file/d/0B4paYLuQGaaocWRaemdsN3I5cFU/view?usp=sharingEO.Web - version 12.0.13.2 Host DateTime Settings: http://joxi.ru/gmv3yv5SLzgN2a
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
The way we understood is that in Moscow time there is no 1/1/2014 00:00:00. The time zone changes at mid-night 12/31/2013. So once the clock reaches 12/31/2013 24:00:00, it goes directly to 1/1/2014 1:00:00. In another word, 1/1/2014 00:00:00 is in fact exactly the same time as 1/1/2014 1:00:00.
To make it more complicated, different JavaScript engine implements this time shift slightly differently. For example, some JavaScript engines automatically adjust 1/1/2014 00:00:00 forward to 1/1/2014 1:00:00. This is what Chrome does and it works fine with the older version. Some other browsers, such as IE does it the other way around, it automatically adjust 1/1/2014 00:00:00 backwards to 12/31/2013 23:00:00, so that 1/1/2014 00:35:00 is the same as 12/31/2013 23:35:00. Both makes sense because it automatically shifts time for one hour. However IE's approach broke our Calendar because when we create a Date object for 1/1/2014 00:00:00 but then later when we get the year of that date, we get 2013. That's the part we worked around with. The 1 hour time must always exist on that day because of the time zone change.
Please let us know if we understood this correctly.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
Quote:The way we understood is that in Moscow time there is no 1/1/2014 00:00:00. he time zone changes at mid-night 12/31/2013. No, Moscow has 1/1/2014 00:00:00. It's our Happy New Year :) Time changed 26.10.2014 at 02.00
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
OK. We will revisit this issue again. :)
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
eo_support wrote:OK. We will revisit this issue again. :) Problem with date 1,2,3,7 January 2014. There is no problem for other date. 4 January 2014, for example, looks good.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Thank you very much for the additional information. We will reply again as soon as this issue is resolved.
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
eo_support wrote:Thank you very much for the additional information. We will reply again as soon as this issue is resolved. Prompt, please, approximate dates solve? Thank you.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi, We have researched this issue and it is a known issue for FireFox: https://bugzilla.mozilla.org/show_bug.cgi?id=1079720Chrome used to have this problem but they have already fixed. FireFox supposes to fix this problem but we do not know when. If we were to "fix" this now, then later it will be broken again when FireFox applies the fix on their side. So we are trying to find a way that won't be affected even if FireFox does fix that problem on their end. Thanks!
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
Quote:Chrome used to have this problem but they have already fixed. No, Nothing in Chrome is not corrected, although the error is dated October. We sent a test example - look it, please Screenshot Chrome: http://joxi.ru/n2YnPaqFoYGEA6Console Chrome: http://joxi.ru/5md0PYahkx4Nm1Chrome is last version: http://joxi.ru/xAeJQDRFpWggryWe know that the bug in Firefox and Chrome, but it can be fixed without waiting for an update from the browser, for example, so instead use the constructor "new Date(2014, 0, 1);" should use var newDate = new Date(); newDate.setDate(1); newDate.setMonth(0); newDate.setYear(2014); we did just that in our other components
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
Quote:We know that the bug in Firefox and Chrome And in browsers, the problem is only one date - 1 January 2014 EO.Datapicker does not work well in a more number - 2,3,7 January 2014
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
We know it works in Chrome. That's why we said Chrome "used to" have this problem, but is already fixed in the current version of Chrome. So older version of Chrome had this problem, but the current version no longer has this problem. Your work around does not work in FireFox if hour is involved. Try the following code:
Code: JavaScript
var newDate = new Date();
newDate.setDate(1);
newDate.setMonth(0);
newDate.setYear(2014);
newDate.setHours(0);
newDate.setMinutes(0);
newDate.setMilliseconds(0);
You will see newDate jumps to 12/31 23:00. This is precisely the problem we are having at the very beginning. We have been testing a different workaround and it seems to be working on our side. However we do not know for sure since you know more about Russian time zone. We will try to provide you an update build as soon as possible for you to test our workaround. Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
We have posted a new build on our download page (it contains EO.Web.dll 12.0.14). This build implemented the other workaround that we have been testing with. Please take a look and see if it resolves the problem for you.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
eo_support wrote:We have posted a new build on our download page (it contains EO.Web.dll 12.0.14).
Thank you, in FF everything is working well, but in Chrome behavior remains the same: problem with date 1, 2, 3 January 2014 4 January 2014 - looks good
|
|
Rank: Member
Groups: Member
Joined: 7/23/2008
Posts: 12
|
Quote:We have posted a new build on our download page (it contains EO.Web.dll 12.0.14).
Quote:Thank you, in FF everything is working well, Hello, any plans to fix that bug in Chrome?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Yes. We have already fixed this internally. We will try to make a new build and send the new build as soon as possible. Thank you very much for your patience.
|
|