The examples/component/wrapper/googleMaps app freezes after a markerClick brings up a dialog: the dialog can be dismissed, but the map remains greyed out and unresponsive.
To reproduce: unzip the Neo github file, install and build all, then npm run server-start, navigate to the app and click on a marker.
Cause: the disabled config value is set to true by the onMarkerClick handler.
Fix: set it to false (or just leave it at the default value of false).
examples/component/wrapper/googleMaps/MapComponent.mjs:
onMarkerClick(data) {
let me = this,
record = data.record.record,
event = data.event;
me.disabled = true; // line 49: change to false to prevent dialog freeze
When me.disabled = true, the "neo-disabled" class is added to the component, and that blocks Dom events per
resources/scss/src/Global.scss:
.neo-disabled {
opacity : v(neo-disabled-opacity);
pointer-events: none;
}
The
examples/component/wrapper/googleMapsapp freezes after a markerClick brings up a dialog: the dialog can be dismissed, but the map remains greyed out and unresponsive.To reproduce: unzip the Neo github file, install and build all, then npm run server-start, navigate to the app and click on a marker.
Cause: the
disabledconfig value is set totrueby the onMarkerClick handler. Fix: set it tofalse(or just leave it at the default value offalse).examples/component/wrapper/googleMaps/MapComponent.mjs:onMarkerClick(data) { let me = this, record = data.record.record, event = data.event; me.disabled = true; // line 49: change to false to prevent dialog freezeWhen
me.disabled = true, the "neo-disabled" class is added to the component, and that blocks Dom events perresources/scss/src/Global.scss:
.neo-disabled { opacity : v(neo-disabled-opacity); pointer-events: none; }