Inconsistent empty list behaviour after dropping multiple routines/events/triggers

[petrduda]

Describe the bug

When dropping all remaining routines/events/triggers, the resulting empty list is not replaced accordingly.

To Reproduce

Steps to reproduce the behavior:

1. Select a database, create a few stored procedures (or events, or triggers, respectively), e.g.:

CREATE FUNCTION `test1`() RETURNS INT(1) NOT DETERMINISTIC NO SQL SQL SECURITY DEFINER RETURN 1; 
CREATE FUNCTION `test2`() RETURNS INT(1) NOT DETERMINISTIC NO SQL SQL SECURITY DEFINER RETURN 1; 
CREATE FUNCTION `test3`() RETURNS INT(1) NOT DETERMINISTIC NO SQL SQL SECURITY DEFINER RETURN 1; 

2. Go to the Routines page.
3. Select all the displayed routines, click "With selected: Drop", click "OK" in the pop-up confirm "Do you really want to delete the selected items?".
4. The procedures are dropped and their rows are removed from the list correctly, but the list header/footer remains displayed.
5. On the other hand, when deleting a single remaining procedure, the empty list is correctly replaced with a text "There are no routines to display."

Expected behavior

After dropping all routines, the empty list is consistently replaced with the "There are no routines to display." text.

Screenshots

After deleting multiple routines:

After deleting single remaining routine:

Server configuration

• Operating system, Web server, Database version, PHP version: https://demo.phpmyadmin.net/
• phpMyAdmin version: 4.9.7, 5.0.4, 5.1.0

Client configuration

• Browser: Firefox 83.0
• Operating system: Ubuntu 20.04