Hi
Since the last release of the Scheduler, there is an issue with the Proxy, that remains in place after the task is created.
Indeed, when you double click on the time grid on the scheduler then a green proxy is displayed; then the EventEditor popup.
Once the save button pressed, then the proxy remains visible and the Event created is behind and is not accessible... Look at the GIF
We could not reproduce with the online demo, so we know that without a tangible test case you won't investigate; nonetheless, we had a few months ago a similar issue (see the post: viewtopic.php?f=44&t=11640) and you did solve it.
Hence, maybe you could either investigate or give us a workaround so as to force and remove the proxy?
(Again this issue came with the new release)
Support Forum
We're under VUE CLI and both Scheduler & Gantt are inside our app, this issue is still there...
We could not reproduce this in the online demo, mainly because you do not have Vertical Mode under VUE in your online demo.
Hence, maybe you could give us the tip on how to remove the Proxy?
Actually when a task is created and the EventEditor is displayed, then the proxy is shown.
Once click on Cancel Button, the Proxy is removed.
Could you tell us how to remove the proxy? Or how not to show the proxy?
Thank you
We could not reproduce this in the online demo, mainly because you do not have Vertical Mode under VUE in your online demo.
Hence, maybe you could give us the tip on how to remove the Proxy?
Actually when a task is created and the EventEditor is displayed, then the proxy is shown.
Once click on Cancel Button, the Proxy is removed.
Could you tell us how to remove the proxy? Or how not to show the proxy?
Thank you
It's very easy to change Vue Simple demo to vertical by adding to schedulerConfig.js file.
With that enabled I tested creation of new events and the proxy disappears for me. See the video: There must be something in your app that triggers it. An override? A CSS? Look at the console output too if there is any error or warning on event creation.
mode : 'vertical'
With that enabled I tested creation of new events and the proxy disappears for me. See the video: There must be something in your app that triggers it. An override? A CSS? Look at the console output too if there is any error or warning on event creation.
Hi Saki
Thank you for taking some time to help us.
Indeed we just run that in the online demo and this is working. But this was made under release 3.0.0 AND our issue occurs in release 2.3.1
The point is this issue occurs only in Vertical Mode and not in Horizontal Mode, which makes us a bit confused.
Moreover, as our app contains both Scheduler & Gantt (module and CSS).
Do you think Gantt CSS is overriding Scheduler CSS ?? or there is a conflict between both CSS?
Thank you for taking some time to help us.
Indeed we just run that in the online demo and this is working. But this was made under release 3.0.0 AND our issue occurs in release 2.3.1
The point is this issue occurs only in Vertical Mode and not in Horizontal Mode, which makes us a bit confused.
Moreover, as our app contains both Scheduler & Gantt (module and CSS).
Do you think Gantt CSS is overriding Scheduler CSS ?? or there is a conflict between both CSS?
Hmm, I have also tried it with Scheduler 2.3.1 and it still works here, therefore I can only guess. First, I'd suspect that some code fails before the proxy is removed: watch the console to see if there's an error message.
Then it could be an override that prevents removal of the proxy after editing is done. Normally, the proxy (div with css class b-sch-dragcreator-proxy), is very volatile and it disappears, and is removed from the DOM, even when you click outside of the dialog which is then closed.
Last tip would be CSS, but more than as a workaround to hide the proxy because it should not be present in DOM in the first place after the editing has been completed or cancelled.
See if you can find div with css class b-sch-dragcreator-proxy in DOM after editing and if yes, then find out why it was not automatically removed.
Then it could be an override that prevents removal of the proxy after editing is done. Normally, the proxy (div with css class b-sch-dragcreator-proxy), is very volatile and it disappears, and is removed from the DOM, even when you click outside of the dialog which is then closed.
Last tip would be CSS, but more than as a workaround to hide the proxy because it should not be present in DOM in the first place after the editing has been completed or cancelled.
See if you can find div with css class b-sch-dragcreator-proxy in DOM after editing and if yes, then find out why it was not automatically removed.
Hi Saki
Thank you very much for your help. We do appreciate that.
We do not have any error in the console once the task is created and the proxy remains visible.
We'll investigate the CSS code you have pointed out...
In order to give you more information about the issue, we have added in the "Basic online demo" a couple of line code we do have in our app (made under VUE CLI)
If you look at our screenshot you could see the Proxy remain in place also.
The step to reach this is :
1) Add the code above in the Basic online demo
2) Double Click to add a Task, the Editor will pop up and a Proxy appears, where the DoubleClick occurs
3) Then, double click again outside, on the scheduler :
a) the Editor is closed BUT the Proxy remain in place
b) the Editor is reopened at the place double-clicked and another Proxy is shown
So, we are wondering if the property "autoClose" set to false could be a part of the issue we do have?
Since, in this case, we do also have an issue with the Proxy?
Thank you very much for your help. We do appreciate that.
We do not have any error in the console once the task is created and the proxy remains visible.
We'll investigate the CSS code you have pointed out...
In order to give you more information about the issue, we have added in the "Basic online demo" a couple of line code we do have in our app (made under VUE CLI)
mode : 'vertical',
................
features: {
eventEdit: {
editorConfig : {
scrollable : true,
closable : false,
autoClose : false,
},
},
},
The step to reach this is :
1) Add the code above in the Basic online demo
2) Double Click to add a Task, the Editor will pop up and a Proxy appears, where the DoubleClick occurs
3) Then, double click again outside, on the scheduler :
a) the Editor is closed BUT the Proxy remain in place
b) the Editor is reopened at the place double-clicked and another Proxy is shown
So, we are wondering if the property "autoClose" set to false could be a part of the issue we do have?
Since, in this case, we do also have an issue with the Proxy?
- Attachments
-
- Capture d’écran 2020-01-04 à 18.47.10.png (192.41 KiB) Viewed 2226 times
Yes, it's this issue already known: https://github.com/bryntum/support/issues/96