From 1dc5daab672cedfe386956911a0a241523f68ecb Mon Sep 17 00:00:00 2001 From: you Date: Sat, 21 Mar 2026 23:06:36 +0000 Subject: [PATCH] fix: stop client WS handler from replacing header path with longest path MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The WS handler was overwriting the group's path_json with the longest path from any new observation. Header should always show the first observer's path — individual observation paths are in the expanded rows. --- public/index.html | 2 +- public/packets.js | 6 +----- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/public/index.html b/public/index.html index 39f9da09..d4a9ea4e 100644 --- a/public/index.html +++ b/public/index.html @@ -84,7 +84,7 @@ - + diff --git a/public/packets.js b/public/packets.js index 31b36c93..f3f0b5bb 100644 --- a/public/packets.js +++ b/public/packets.js @@ -276,11 +276,7 @@ if (p.observer_id && p.observer_id !== existing.observer_id) { existing.observer_count = (existing.observer_count || 1) + 1; } - // Keep longest path - if (p.path_json && (!existing.path_json || p.path_json.length > existing.path_json.length)) { - existing.path_json = p.path_json; - existing.raw_hex = p.raw_hex; - } + // Don't update path — header always shows first observer's path // Update decoded_json to latest if (p.decoded_json) existing.decoded_json = p.decoded_json; // Update expanded children if this group is expanded