DOM html appoint you svga rights to render events not DOM

[julientype]

Problem statement

Expected Behavior

Actual Behavior

Steps to Reproduce

1. Start by..
2. Next, do..

Stack Traces

Replace with error stack trace.

Operating System and Browser

Additional Information

[RoboErikG]

Could you please provide more detail on the issue and how to reproduce it?

[julientype]

svga is not DOM .... like an iframe in a HTML page they send message to each other
keypress is a nasty one ...is it DOM or SVGA that govs the interprets to the key board actions
key press is done not by DOM but the SVGA engine
so the keyup even is sent to DOM because svga is done rendering its key press event....
this is where a validate event can fire to DOM it cant be done by combination of both to render a keypress events it just dispatch to the other by a key up event that svga cars nothing about yet DOM does for its end input ...
keyboard press can only be done by one.... DOM vs svga engine.... pick
so a block is an iframe as a svga document to an html page and both cant process a keypress event .. master slave relation... svga holds key-press and dom holds key up event dispatch from svga agent to dom...
DOM html appoint you svga rights to render events not DOM

[RoboErikG]

I'm still not sure I follow.

What are the steps that would cause an issue? Create an SVG with ...?

Why is it an issue? It causes ...?

[julientype]

tk i did solve it .... it had to do with validating a text-input....
i need from the user a to z only input at length 20 ...
what happens with the input view will only upgrade after the lost focus of the Block not during editing of input field..... it looks buggy on the user....
so the user will see [ dfff23@4 ] where should only be [ dfff ] yet it corrects it self on the lost focus event
i just started testing your APIs

tk.... Julien

[RoboErikG]

Ah, that updating issue in specific is fixed in the release going out this week.

[julientype]

I found anew type of bug....
i;m running a custom generator file......
i have a root block you cant delete and the return code work grate ....
next i try drag and drop a new bock into place..... <----error
as i select it to drag its inserting its return code .........<---not good
basically this should not happen until i drop it into place or remove.....
where block A will request block B once in place....... a chain request to sub block connection

MYGenerator['column_def'] = function(block) {
var str ='test return code';
return str;
};

nasty error shows up in DOM and all i did was drag drop remove add remove with 2 blocks......
Uncaught (in promise) DOMException
this error is caused by blocks no longer in its connection line yet the call is still running.....
I am i missing something ???? like parent child index

here is what i mean.... a root node starts the call process nothing else..... a calls b because its connected and b calls c because a requested it not b and c is connected to b....

root node is not a workplace it runs and commands return code events drag drop is work-space events....
the root node can be a doc generator like a form creator with other type of root node generators embedded in it like a script root node......

[RoboErikG]

That's probably related to #2646 The easiest way to fix it is to check workspace.isDragging() in the code that calls the generator and to skip generating while a drag is in progress.

If you have further problems I'd recommend asking on the forum and including information like

• What your setup looks like
• What you're trying to do
• The error messages or console logs you're getting
• Any code you think is related to the issue

We are faster to respond on the forums and providing a clearer explanation of what you're doing and the problem will make it easier for folks to answer your question.