Make the web console waiting screen's tasks pointer clickable: while a build runs, Task and the tasks tab's own name (Phase N tasks) show bold in the highlight color and open that phase's tasks tab

This commit is contained in:
jparkerweb committed 2026-10-04 15:52:20 -07:00
1 parent 48830c1afb
commit 739e56c5cf
29 files changed
+575 -112

No files matched your search

+1
View File
@@ -46,6 +46,7 @@ All notable changes to Plan2Code will be documented in this file.
- **Windows**: the folder picker (the launcher's desktop shortcut and the Workspace **Browse…** button) now opens centred and in front of other windows instead of behind the terminal.
- **Launcher**: before asking which CLI to use, `plan2code` says what it is about to do and that running `/plan2code` inside your agent works too.
- **web-console**: the session meter now weighs the work a session actually did instead of a flat amount per step. A built phase scores one point per 3 tasks it completed (rounded up), plus 1 for Implement + Review, so a twelve-task phase weighs four times a three-task one; the agent reports the count as `run.tasks`. Every 2 questions you answer on the page add a point to the skill you answered them in, so a long back-and-forth in Plan or Pathfinder counts for more than a short one. Each Pathfinder research question adds 1 through a new `pathfinder-research` event, since research fills the context with nobody answering anything. The levels move to match: yellow from 5 points, red from 10, and the ring is full at 15.
- **web-console**: while a build runs, the waiting screen's pointer to the tasks list is now clickable. **Task** and the tab's own name (say **Phase 6 tasks**) show bold in the highlight color, and either one opens that phase's tasks tab.
### 🐛 Fixed
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the
+12
View File
@@ -1997,6 +1997,18 @@ kbd {
}
.waiting-pane h2 { font: 600 23px/1.3 var(--serif); color: var(--ink); margin: 0; }
.waiting-pane p { margin: 0; }
/* The words that open the tasks tab: bold in the highlight color, a button
that reads as part of the sentence. */
.waiting-jump {
font: inherit;
font-weight: 700;
color: var(--accent);
background: none;
border: 0;
padding: 0;
}
button.waiting-jump { cursor: pointer; text-decoration: underline; text-decoration-color: var(--accent-line); text-underline-offset: 3px; }
button.waiting-jump:hover { text-decoration-color: var(--accent); }
/* Once the work is under way Planny steps back a size, and the ring in
front of the stage name carries the "still going" signal instead. */
.waiting-pane .pose-stage { height: 130px; transition: height 0.35s ease; }
+29 -8
View File
@@ -3327,15 +3327,36 @@ function renderWaiting(main) {
}
pane.appendChild(title);
pane.appendChild(el("p", null, doing));
pane.appendChild(
el(
"p",
null,
docs().length
? "The tabs above fill in as it goes. You can follow along with live `Task` updates in the `Phase tasks` tab. If Plan2Code needs you, the question appears here on its own."
: "If Plan2Code needs you, the question appears here on its own."
)
if (!docs().length) {
pane.appendChild(el("p", null, "If Plan2Code needs you, the question appears here on its own."));
return;
}
// "Task" and the tasks tab's own name both open that tab, so the pointer is
// one click from what it points at. A build posts it as `phase` ("Phase N
// tasks"), a quick task as `tasks`; with neither the words stay plain.
const list =
docs().find((d) => d.id === "phase") ||
docs().find((d) => d.id === "tasks") ||
docs().find((d) => /\btasks\b/i.test(d.title || ""));
const jump = (word) => {
if (!list) return el("strong", "waiting-jump", word);
const b = el("button", "waiting-jump", word);
b.type = "button";
b.addEventListener("click", () => {
view = "doc:" + list.id;
render();
});
return b;
};
const p = el("p");
p.append(
"The tabs above fill in as it goes. You can follow along with live ",
jump("Task"),
" updates in the ",
jump((list && list.title) || "Phase tasks"),
" tab. If Plan2Code needs you, the question appears here on its own."
);
pane.appendChild(p);
}
// A notice is context for the question it sits beside, so it lives inside the