Before answering your points, I figured out that this problem is specifically related to Toolset only.
For, e.g., I added a View block in the Sample Page and I encountered problem #4. After saving the page and trying to navigate away, I started encountering problem #4, but as soon as I removed the View block, the problem also vanished away.
Do you feel it would be more feasible if you give you access to the sandbox installation, where you would be free to do whatever you like.? However, you are free to do whatever changes you want in the present installation also. Either way.
I would like to see your experience in Firefox when logged in as the same Toolset user. Please open a new private window in Firefox, and log in as the Toolset User. In the Firefox menu, go to Tools > Browser Tools and turn on the Web Developer tools. Create a screen recording or a series of screenshots so I can see the problems you have described in the WordPress Archive editor where live preview is not working as expected. You can upload a screen recording video to Drive or Dropbox and provide a download link here for me.
I will get this done by tomorrow.
If you create a new WordPress Archive, this one for a different post type, like Posts or Pages instead of , do you see similar problems in both WordPress Archive, or is the problem only in the Product archive?
Yes, I encountered this problem when creating a new archive.
Yes, it seems there was a CSS conflict between the GeneratePress theme and Toolset Blocksthat is breaking the display:flex style applied by Toolset blocks. GeneratePress adds this style in main.min.css:
Got it. Would there be a quick fix in the near future so that I don't have to add the request CSS code on each new site?
You are correct, this is a limitation of the pagination block. If you'd like to see this block's configurations updated to include more flexibility, like Typography configurations, feel free to submit a feature request to our developers here:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
Actually, I wouldn't worry much about this. Just because of me or a few other users, the developers aren't going to be convinced that typography options are also needed for pagination. I am speaking from my personal experience, and hence I no longer take much interest in submitting feature requests unless otherwise deemed absolutely necessary. I would leave this part for the developers.