editTable | jQuery editTable is a very small jQuery Plugin ( ~1Kb | Plugin library

Adding ajax to the orderList with processing and updating the orderList solved the issue.

the first error is because you forgot to declare the variable f, you declared only the variables r and c above.

the second is in the function DeleteRow() there is an indexing error because it finds a negative value when deleting the last row. If you don't even want him to delete the last row, I suggest using a Try-Catch to deal with this error.

It all boils down to the question of how to use an editable table and to keep the data in the client and the server in sync.

You used DTedit a library which I am not aware of and never used, so I show you a DT only solution. Looking at the docs of DTedit I also think that the way how you tried to implement it (in particular mixing it w/ ordinary DT) is not how it meant to be used, but it is rather a replacement possibility for DT)

Here we go (explanation below):

From your code

You can't make the popup modal on modern browsers. (There used to be a different method you could use for popup modals, but it's deprecated now.)

By default, that window should appear in front of the window that opens it. You can also respond to clicks on the opening window's document by calling focus on the window returned by open, to bring that other window to the foreground (stopping when you see the unload event from the popup).

If what you're showing in the modal doesn't have to be a separate window, you might consider not using a separate window at all, but instead using an absolutely-positioned div or similar with an element behind it that covers the entire remainder of the window so that it can prevent clicks and similar from reaching the elements underneath it. But if it has to be a separate window, you don't have much you can do other than the focus thing.

You can use List to receive the modified data.

The name attribute in the view needs to match the cutDatas parameter that Edit action receives.

In addition, the submit button does not need to add asp-controller. This will cause you to click on the button and enter the default method of Home instead of Edit action.

And the index for adding rows in js needs to be added on the basis of model data count.

React native only has a single js thread, so performing expensive calculations will clog up your app (you won't be able to interact with it).

That being said, if your loading time is significant enough to display the spinner, you should probably do that asynchronously, and not right after setState() (if it's fast enough, then you probably don't need a spinner to show up for 100ms).

When you call setState() and then do a bunch of work, the component will not re-render before that work is done, so two setState()-s is not the issue here. It wouldn't work even if you had only one.

Lucky for you, react-native's ActivityIndicator component's animation runs on native UI thread, so it isn't affected by the js thread performing expensive work. So, what you can do is delay the work a little bit to allow for the setState() to take effect. Here's the code:

AFAIK, there's no way to make all header fields editable by default, but you could customize the body template, and dynamically render the data using v-for and the v-edit-dialog for each item. For example...