Mirrored_Repos/DarkflameServer
1
0
Fork 0
mirror of https://github.com/DarkflameUniverse/DarkflameServer.git synced 2026-10-02 02:43:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(dashboard): pages about one row update in place instead of reloading

Browse Source 
Nav.refresh() fetches the current page and compares the server's HTML
now with the HTML the page started from; only what differs is patched
into the live page (text, attributes, class changes, rows added or
taken away). Typed input stays (the browser keeps what the user
changed while the default value follows the server), and parts built
by the page's scripts are left alone. Where a patch would lose
script-built or script-bound parts, or the page's layout changed, the
page is swapped in again with its scripts, keeping the scroll
position, open tabs, open folding parts and typed input; while the
user is typing it offers a refresh instead.

Live.refreshPage (account, character, bug report and play key pages)
uses it instead of reloading the page, and the "This changed while you
were editing" banner's Refresh does too.

Check: open a play key; in another tab change its uses or active
switch: the first tab's values and badge change without a reload,
and notes typed there stay. Same on a bug report page with a half
typed resolution when it's resolved elsewhere. On a character page,
an in-game save updates it without losing the open tab or scroll.
Test: NavRulesJs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Aaron Kimbrell
2026-09-29 01:57:17 -05:00
parent f58255ab8a
commit b66bae6a9c
5 changed files with 215 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/Dashboard.md
View File

@@ -360,8 +360,9 @@ reports are kept as the record of what happened.
## Live updates
Pages update on their own: world servers tell the dashboard (through master) as soon as they write something it shows,
and it pushes that to open browsers. Pages about one thing (a character, an account) reload in place when it changes,
unless you're typing, in which case they offer a refresh instead.
and it pushes that to open browsers. Pages about one thing (a character, an account) update in place when it changes:
only the parts the server now shows differently change, and what you're typing stays. When the page can't be patched
that way (its layout changed) and you're typing, it offers a refresh instead.
Moving between pages doesn't reload the dashboard: the next page is fetched and swapped in, and the menu, the top bar
and the live connection stay. A thin bar at the top shows while it loads; if it can't be fetched, the page says so with
@@ -372,8 +373,9 @@ them load normally. Leaving a page with unsaved changes (Settings, Vanity) asks
For page scripts (`static/js/nav.js`): listeners a page adds to `document` or `window`, its `setInterval` timers, its
`Live` watchers and its DataTables are removed when another page is swapped in; its scripts run again when it's opened
again, and `DOMContentLoaded`/`load` handlers they add run once they have all run. Elements a page appends to `<body>`
are removed unless marked `data-nav-keep`. `Nav.go(url)` opens a page. `document` gets `dash:page` after a page is
swapped in and `dash:leave` before. A page that must always load on its own adds `data-nav="reload"` to any element; a link with `data-nav="off"`
are removed unless marked `data-nav-keep`. `Nav.go(url)` opens a page, `Nav.refresh()` updates the current one in place.
`document` gets `dash:page` after a page is swapped in, `dash:leave` before, and `dash:refreshed` after an in-place
update. A page that must always load on its own adds `data-nav="reload"` to any element; a link with `data-nav="off"`
always loads normally.
View choices you make on the pages (show staff, filters, the 3D viewer's switches, ...) are saved to your account, so