Add link to GitHub issue from inline issue (#1132)

SHA: 6fee9c9
Reason: push, by whimboo

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: gsnedders

index.html

@@ -8,7 +8,7 @@
   <meta content="Bikeshed version d113b2e81, updated Tue Jun 9 14:57:55 2026 -0700" name="generator">
   <link href="https://www.w3.org/TR/webdriver-bidi/" rel="canonical">
   <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
-  <meta content="d636c85720119ff2f7d5371c01e1ac63168e249f" name="revision">
+  <meta content="6fee9c9554eecad9790e86c302b247b1540b32f0" name="revision">
   <meta content="dark light" name="color-scheme">
   <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
 <style>
@@ -657,7 +657,7 @@
 </p>
    <h1 class="no-ref p-name" id="title">WebDriver BiDi</h1>
    <p id="w3c-state"><a href="https://www.w3.org/standards/types/#ED">Editor’s Draft</a>,
-    <time class="dt-updated" datetime="2026-06-29">29 June 2026</time></p>
+    <time class="dt-updated" datetime="2026-07-15">15 July 2026</time></p>
    <details open>
     <summary>More details about this document</summary>
     <div data-fill-with="spec-metadata">
@@ -4652,8 +4652,8 @@ <h5 class="heading settled" data-level="7.3.3.2" id="command-browsingContext-cap
      <p>Let <var>document</var> be <var>navigable</var>’s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/document-sequences.html#nav-document" id="ref-for-nav-document⑦">active document</a>.</p>
     <li data-md>
      <p>Immediately after the next invocation of the <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/imagebitmap-and-animations.html#run-the-animation-frame-callbacks" id="ref-for-run-the-animation-frame-callbacks">run the animation frame callbacks</a> algorithm for <var>document</var>:</p>
-     <p class="issue" id="issue-b2b83ca0"><a class="self-link" href="#issue-b2b83ca0"></a> This ought to be integrated into the update rendering algorithm in
- some more explicit way.</p>
+     <p class="issue" id="issue-b2b83ca0"><a class="self-link" href="#issue-b2b83ca0"></a> This ought to be integrated into the update
+ rendering algorithm in some more explicit way. <a href="https://github.com/w3c/webdriver-bidi/issues/1131">[w3c/webdriver-bidi Issue #1131]</a></p>
     <li data-md>
      <p>Let <var>origin</var> be the value of the <code>context</code> field of <var>command
  parameters</var> if present, or "viewport" otherwise.</p>
@@ -5616,8 +5616,8 @@ <h5 class="heading settled" data-level="7.3.3.9" id="command-browsingContext-pri
       <p>Let <var>document</var> be <var>navigable</var>’s <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/document-sequences.html#nav-document" id="ref-for-nav-document①②">active document</a>.</p>
      <li data-md>
       <p>Immediately after the next invocation of the <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/imagebitmap-and-animations.html#run-the-animation-frame-callbacks" id="ref-for-run-the-animation-frame-callbacks①">run the animation frame callbacks</a> algorithm for <var>document</var>:</p>
-      <p class="issue" id="issue-b2b83ca0①"><a class="self-link" href="#issue-b2b83ca0①"></a> This ought to be integrated into the update rendering algorithm
- in some more explicit way.</p>
+      <p class="issue" id="issue-b2b83ca0①"><a class="self-link" href="#issue-b2b83ca0①"></a> This ought to be integrated into the update
+ rendering algorithm in some more explicit way. <a href="https://github.com/w3c/webdriver-bidi/issues/1131">[w3c/webdriver-bidi Issue #1131]</a></p>
       <ol>
        <li data-md>
         <p>Let <var>pdf data</var> be the result taking UA-specific steps to generate a
@@ -24909,13 +24909,13 @@ <h2 class="heading no-num no-ref settled" id="issues-index"><span class="content
  an error here? What error code do we want? Is there going to be a problem
  where local ends parse the implementation-defined strings to figure out
  what actually went wrong? <a class="issue-return" href="#issue-ceba1469" title="Jump to section">↵</a></div>
-   <div class="issue"> This ought to be integrated into the update rendering algorithm in
- some more explicit way. <a class="issue-return" href="#issue-b2b83ca0" title="Jump to section">↵</a></div>
+   <div class="issue"> This ought to be integrated into the update
+ rendering algorithm in some more explicit way. <a href="https://github.com/w3c/webdriver-bidi/issues/1131">[w3c/webdriver-bidi Issue #1131]</a> <a class="issue-return" href="#issue-b2b83ca0" title="Jump to section">↵</a></div>
    <div class="issue"> There is an open discussion about the behavior
 when closing the last <a data-link-type="dfn" href="https://html.spec.whatwg.org/multipage/document-sequences.html#top-level-traversable">top-level traversable</a>. We could expect to close
 the browser, close the session or leave this up to the implementation. <a href="https://github.com/w3c/webdriver-bidi/issues/170">[w3c/webdriver-bidi Issue #170]</a> <a class="issue-return" href="#issue-04e2b4be" title="Jump to section">↵</a></div>
-   <div class="issue"> This ought to be integrated into the update rendering algorithm
- in some more explicit way. <a class="issue-return" href="#issue-b2b83ca0①" title="Jump to section">↵</a></div>
+   <div class="issue"> This ought to be integrated into the update
+ rendering algorithm in some more explicit way. <a href="https://github.com/w3c/webdriver-bidi/issues/1131">[w3c/webdriver-bidi Issue #1131]</a> <a class="issue-return" href="#issue-b2b83ca0①" title="Jump to section">↵</a></div>
    <div class="issue"> There is a race condition in the algorithm as written because by the
  time we try to navigate the target session history entry might not
  exist. Once we support waiting for history to navigate we can handle this