index

scrbl/rktwebviewqt-internals.scrbl

@@ -1,7 +1,7 @@
 #lang scribble/manual
 @(require racket/runtime-path)
 
-@defmodule{racket-webview/internals}
+@bold{Internal component:} @tt{racket-webview/internals}
 
 @title{Qt WebView Backend Architecture}
 @author[@author+email["Hans Dijkema" "hans@dijkewijk.nl"]]
@@ -44,7 +44,7 @@ reconfigure the organ. No attempt is made to unify the instruments. Such efforts
 
 From the outside, one hears only a simple exchange: a call, a response. Internally, the balance is carefully maintained. For now, this is sufficient. And it holds.
 
-@section{Overview}
+@section[#:tag "rktwebview-qt-internals-overview"]{Overview}
 
 This backend provides a webview implementation by delegating all GUI and browser
 functionality to a separate Qt process.
@@ -93,7 +93,7 @@ thread.
 From the caller’s perspective, a synchronous call returns only after the GUI
 thread has completed the action.
 
-@section{Event Delivery}
+@section[#:tag "rktwebview-qt-internals-event-delivery"]{Event Delivery}
 
 Many relevant events are not tied to a specific command. Page loading, navigation
 attempts, window movement, and JavaScript-originated events are delivered through