Fauxton makes repeated requests for design document info but does not update web UI with new data received

[ctsrc]

Steps to reproduce:

1. Have a database in CouchDB with a design doc index that is currently being updated.
2. Go to the "metadata" page for this design doc in Fauxton. Let's say http://localhost:5984/_utils/#/database/users/_design/usernames/_info as an example.
3. Observe in networks tab in browser dev tools that Fauxton is making requests to CouchDB for info every few seconds, yet it's not updating the page with new data.

For example, I load a Fauxton page like http://localhost:5984/_utils/#/database/users/_design/usernames/_info and it shows the following info on the page:

_design/usernames Metadata

Index Information

Language: Javascript

Currently being updated? Yes

Currently running compaction? Yes

Waiting for a commit? Yes

Clients waiting for the index: 12

Update sequence on DB: 229000

Processed purge sequence: 0

Actual data size (bytes): 1,716,553,382

Data size on disk (bytes): 2,189,875,620

MD5 Signature:

Observe in the browser dev tools that as mentioned this Fauxton page is then repeatedly making requests to in this case http://localhost:5984/users/_design/usernames/_info. A response from this looks like:

{
    "name": "usernames",
    "view_index": {
        "updates_pending": {
            "minimum": 185234,
            "preferred": 185234,
            "total": 185234
        },
        "waiting_commit": true,
        "waiting_clients": 12,
        "updater_running": true,
        "update_seq": 230515,
        "sizes": {
            "file": 26957189824,
            "external": 2205166319,
            "active": 1728786570
        },
        "signature": "e10391178cb4888f196078f0015b77bf",
        "purge_seq": 0,
        "language": "javascript",
        "compact_running": true,
        "collator_versions": [
            "153.121"
        ]
    }
}

So all of the info that is being shown on the page is actually getting fresh data every few seconds. But this is not shown to the user. The page remains unchanged from how it looked when it loaded, even though it is retrieving fresh data.

It would make a lot of sense IMO, to update what is shown on the page every time the Fauxton web UI keeps making this info request anyway.