You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sync reused-pane tab metadata and fix address-bar local check
When ldh:rdf-document-response reuses a same-origin tab pane for a new
URI, also update the matching tab <li>'s data-uri, <a href>, title, and
label. Downstream lookups in ldh:RenderTab and ldh:DocumentNavigate key
on data-uri, so a stale data-uri silently mismatched and left the tab
showing the previous URI.
Switch the address-bar "is local?" check in ldh:DocumentNavigate from
ldt:base() to lapp:origin(ldh:request-uri()) || '/'. ldt:base() reads
the active pane's data-base, which mis-classified URIs while a proxy
pane was still active: same-origin proxy URLs got the bar cleared, and
switching back to a local doc left the bar populated.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
<!-- update address bar input: show external URI, clear for local docs -->
821
+
<!-- use browser origin (not ldt:base()) so the check is correct even when an external tab is active: ldt:base() reads the active pane's data-base, which would mis-classify same-origin proxy URIs as "local" and cross-dataspace URIs as "external" mid-switch -->
0 commit comments