Problem: I have a View that shows posts and includes an Edit Post Link in each result. I have set up the Edit Post Form in a separate Content Template, and this seems to be working as expected. After editing a post by clicking the Edit Post Link and submitting the Edit Post Form, I would like to redirect back to the page containing the View of posts and scroll to the item that was just edited so it is visible in the browser.

Solution: You can add an anchor tag to each item in the View's loop, then use the Forms redirection API to redirect to that page and scroll to the anchor using a URL hash with the anchor name. This could only work in a View that does not use infinite scrolling, because the results must all be present on the page when the page loads in order to scroll to the correct location. If the View uses pagination, you'll also need to calculate the correct page number to jump to the correct set of results.

Anchor syntax using post ID to create unique anchor id:

<a name="result-[wpv-post-id]"></a>

or

<a id="result-[wpv-post-id]"></a>

If you add an anchor in the View loop, using the syntax shown above, you can redirect and scroll to that specific element by including the corresponding name in a URL hash like so:
https://yoursite.com/page-with-view/#result-12345

Example redirection API implementing this deep-linking syntax:

// Redirect and scroll to the edited post in View results
// Toolset support: https://toolset.com/forums/topic/scroll-to-last-used-item-in-a-view/
add_filter('cred_success_redirect', 'tssupp_deep_link_after_edit',10,3);
function tssupp_deep_link_after_edit($url, $post_id, $form_data)
{
    if ($form_data['id']==12345)
        return 'https://yoursite.com/page-with-view/#result-' . $post_id;
    
    return $url;
}

You would replace 12345 with the numeric ID of the edit post Form, and replace https://yoursite.com/page-with-view/ with the full path to the page containing the View. If there are multiple pages containing the same View, you'll need something more complex here to determine the proper redirection location.

Problem:
The user has a grid view that should display 2*3 elements, and it was displaying 3 rows with (3,2,1) columns.

Solution:
The issue was caused by a nested <em> HTML tag in the custom field used inside the loop of the view. That breaks the validity of the whole view and Toolset generated an undesired grid.
Once we removed the child "em" tag, the issue was fixed.

Problem:
Date time field CSS removed with ajax filter view

Solution:
Toolset offers the ajax event hook: js_event_wpv_parametric_search_results_updated

Which you can use the add your custom CSS code and try to apply it using the jQuery.

Relevant Documentation:
=> https://toolset.com/documentation/programmer-reference/adding-custom-javascript-code-to-views-that-use-ajax/
=> https://toolset.wiki/article/trigger-js-event-after-ajax-finished/