usability - Expected behaviour after file upload

What is the expected behavior of a file uploader, after the file is uploaded?

Here is a use case where the expectation of the users depend on the current status.

1. 
   

   The user sees a large list of files in a table. The table is using lazy loading that appends new data once the end of the scroll-bar is reached. The scrolling in my eyes is a complex tasks that will take the user quite some time. Once the desired file is found, the user can click it to see further options.

   
   

   Now the user decides to upload a new file. Probably the expectation is not that this new files will be visible immediately, because of the current scolling-position. Also a "refresh" of the current view could lead to the "lose" of the selected file.

   
   
   

   

   
   


2. 
   

   The user is seeing a empty or poorly filled list and decides to upload new files. The expectation now will be, that the new files have to be visible right after the upload.

   
   

   

   
   

What would be the best way to tackle this problem? Implement one standard behavior that might be counterproductive for certain use cases (see 1.) or should there be some kind of intelligence in the uploader, that makes sure that the current state is protected no matter what. Even if this could lead to make the user manually refresh a view (see 2.).

Answer

Use a general upload feedback popup at some peripheral position which notifies the user about the success/error of the upload and if it was successful, give an option for the user to jump there in the view. This way, they get they feedback which does not interfere instantly with the lazy loading list, but they still have the option to locate the freshly uploaded file.