Hi Windy Again,
We are suddenly getting a Not Authorized response when viewing Windy in our application. This has happened before and I continuously asked how we could check for this happening in the future and deal with it politely, but you completely ignored me. "It is working now"
Euan
@Korina Any update on this? This is causing us major issues
@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 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
@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
@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
