@ss-nick Out of interest what was the issue?

@Korina When will this be available via the API?

Hi Windy,

Just wondering if you have any planned releases this year?

Would be nice if you upgraded to the latest version of Leaflet and also if you used the standard version of Leaflet (not forked).

Thanks

Euan

@mates-dolda
Working here too. Thanks Martin

@ss-nick I sent a message to @marekd earlier on too. He used to look after new releases and tried at one point to improve the Windy release process to prevent issues like this. But for the past year not heard anything about new releases etc

@Korina Any update on this? This is causing us major issues

Same issue here, going on now

@ss-nick Getting the same issue here

@marekd said in API beta test:

checkboxes and radio buttons are considered as readonly inputs in browsers by default.

@marekd I have never seen a checkbox or radio button having a default readonly value in all my life. Please can you share any documentation you have on this?

Mozilla's documentation says it is not default.
https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/readonly

Prior to your release on Monday morning, this was working as expected.

@marekd We will need to discuss this internally. Initial feeling is that we would rather stay as close to a standard leaflet implementation as possible. Windy is a small part of our application.

@marekd can you reproduce the above CSS issue? I could create a simple page and set this up if you would like.

Euan

@marekd

I can override the CSS with

    #windy .form-group input:read-only {
        cursor: initial; /*This is like a weird bug where it was showing checkboxes as disabled even if the input was not read-only*/
    }

but seems like a bug at your side.

@marekd We have made some progress with the issues using the following:

windyInit(options, windyAPI => {

                const { map, picker, utils, overlays, store, broadcast, particles } = windyAPI;

                let baseLayer = W.map.baseLayer;

                W.map = W.map.map;
                W.map.baseLayer = baseLayer;
}

The rest of our code uses W.map to address the map, so we have to assisn W.map.map to it. But this then lost w.Map.baseLayer, so we need to reassign it too.

This has brought our application back to life, but one need issue could you look at?

We create a form on the map to control turning on / off other layers. Since the new version of Windy we are now getting a "cursor: not allowed;" when hovering over the checkboxes shown in the screenshot.

The CSS is matching on input:read-only but our input checkboxes are not read only.... As you can see in the screenshot nothing is set to read only. But on hover of those inputs you get :

@idefix37 In our application, my idea was to include the magnetic course as well as the true course in the list of waypoints in the passage plan. Not sure we actually need the Compass Rose, but to have the deviated course would be nice.

@mared Could someone please help us? This version has completely broken us.

@idefix37 I don't think it should be in Windy, just wanted to share a potential solution with @saugeener

Having a Compass Rose could be beneficial for paper chart navigation. However the UKHO also announced last week that they are aiming stop paper charts from the end of 2026.

@marekd

Hi @marekd, could you please tag us in future? You have taken down our application in production this morning. Issues been reported to support.

@nesro I have emailed a login to support@windy.com

@nesro said in Windy - Errors in lib.js started on 1st August:

support@windy.com

I can see that you released a new version at 9am this morning. Before that we had no issues.

The errors before were when we were using an older version of libboot.

Using your updated version of libboot.js we get the following:

I think the error is happening when we are adding controls to the map, but it is hard to know exactly.

const options = {
    key: 'ourKey',
    verbose: false,
    zoom: 3,
};

function SetupMap() {
    try {

            localwindy = windyInit(options, windyAPI => {

                const { map, picker, utils, overlays, store, broadcast, particles } = windyAPI;

                map.removeLayer(W.labelsLayer);

                MapState = new MapStateManager(map);
                map.MapState = MapState;

                map.addControl(L.control.zoom({
                    position: 'topleft'
                }));

//more code

}
}

@Windy

Created this in Developers instead.

This ticket can be deleted

Hi Windy,

We first noticed we were getting errors from lib.js this morning, errors shown in Chome Dev Console:

Screenshot 2022-08-01 104605.png Screenshot 2022-08-01 105634.png Screenshot 2022-08-01 105657.png

Can you please investigate this?

Let me know if you need any more information. We were not getting these errors last week.

Euan