jQuery UI Widgets Forums Chart safari crash when time change is in chart

This topic contains 2 replies, has 2 voices, and was last updated by  vojta 3 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author

  • vojta
    Participant

    Hello,

    We have multiple JQW-charts on our page. I came across a problem when there was a time change on 31/03/2019 (CET (+1) to CEST (+2)).
    I use MacOS and latest version of Safari web browser. When the time-change date is within range of the graph xAxis (e.g. the xAxis interval is 2019/03/29 (CET) – 2019/04/05 (CEST)) the whole browser tab freezes. JS console stops responding and the only solution to “fix” is close the tab.
    Google Chrome and Mozilla Firefox both work well, this problem is Safari only (as far as i know).

    The problematic option, that causes this problem is baseUnit: "minute" in settings.xAxis.
    if baseUnit is set to “hour” or “day” it works fine.

    var settings = {
        source: data,
        title: "Line Chart",
        xAxis: {
        	dataField: 'date',
            type: 'date',
            baseUnit: 'minute',

    jQWidgets version: v3.7.1 (although i tried it with the newest version and problem was the same)
    jQuery version: 1.11.1 (tried 2.x.x and 3.x.x and doesn’t work either)
    Safari version: 12.1, 12.0
    MacOS version: 10.14.4

    In THIS EXAMPLE is a small sample of chart, that freezes Safari.

    I hope that I managed to give all the information needed.

    Thanks for suggestions and help!
    Vojta

    (example url: http://jsfiddle.net/5dwgq73r/2/)


    admin
    Keymaster

    Hi vojta,

    baseUnit: ‘minute’ represents a minute and when the range is in multiple days, the Chart needs to render very many points. We suggest you not using this with such ranges.

    Best Regards,
    Peter Stoev

    jQWidgets Team

    https://www.jqwidgets.com/


    vojta
    Participant

    Hi Peter,

    Thank you for quick reply.

    Ok, thanks for the advice. Event though that’s not really the point of this thread. The problem with crashed/lagged Safari occurs even when the range is only 24 hours (1440 minutes = 1440 points) – this is for 2019/03/31 00:00:00 – 2019/04/01 00:00:00, in this case would only be 23 hours because of the time change.

    And when the date does not contain time change, it works really fine.
    You can try that yourself if you edit line 5 of the example I gave:
    const date = new Date(2019, 02, i, j, (j*10)%60, 0);
    change to:
    const date = new Date(2019, 03, i, j, (j*10)%60, 0);
    and it won’t crash Safari anymore.

    Thanks a lot,
    Vojta

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.