When the new versions of the search blocks are retrieved, they are appended to the end of the region they belong to. This means that any non-search blocks float to the top after any change to the search query. Blocks are usually put in a certain order for a reason, so it's better to preserve it if we can.

Instead of appendTo(), I propose the response callback uses replaceWith() to change the blocks.

CommentFileSizeAuthor
replaceWith.patch1.15 KBIsland Usurper

Comments

jonvk’s picture

jonvk commented

I agree this should be fixed. I've tested it on a small demo site and it seemed to work fine, but I will try and get it on something with more content before committing.