January 7th issue

    While working on one of the projects, a rather interesting bug was discovered, which, as it turned out later, manifests itself not only in “self-written” calendars, but also in popular open-source libraries. The problem is the inability to choose January 7th . In some calendars this date is simply missing :
    image
    If you select the 6th number (which stands in place of the 7th), then ... the 6th number is selected.

    The bug is observed (according to preliminary estimates) under Windows 8 .

    UPD: The nature of the problem is disclosed here . It's all about RTZ2 after Microsoft Update KB2998527.

    UPD2: 0xy : the problem is observed not only in Firefox, but also in mobile versions of various browsers.Details (plus bug fix).

    Some details under the cut.

    A quick run on the Internet showed the presence of this problem in a wide range of calendars. In most cases, the 7th number is shown, but it cannot be selected:

    image

    Since almost all js-calendars are used for calculations Date, it is likely that under certain circumstances the use of the latter can lead to some problems for users on January 7th .

    Most recently, a post appeared on the hub about the problems of date and time in JS , where the comments discussed the issue of different behavior Datein different browsers. And, apparently, a vivid example of one of such problems was found.

    The bug was observed inFirefox (latest version, Windows 8), there is evidence that the bug was also detected under Chrome (latest version, Windows 8). We weren’t able to catch it (there is no Windows 8 in the office), but the growing dissatisfaction of some customers (in our case, the hotel) indicates that there is a problem. And, it seems, this is somehow connected with Windows 8. On the same computer in Internet Explorer, the calendar worked correctly. There is information that after upgrading to Windows 8.1, the problem resolves itself. There is very little time left until this date, so I decided to warn that someone might not receive customers on January 7, but hemorrhoid a lot of angry calls. Forewarned is forearmed.

    The nature of the problem probably lies in the fact that each browser implements an object in its own way Date, which means that time can vary from browser to browser. But here the bug is observed with reference to the system. Maybe someone from the Habrachians can comment on such an interesting behavior?

    Also popular now: