morluto/rea

Fork

You've already forked rea

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

Code Issues 1.3k Projects Packages Wiki Activity

[PR #5621] [MERGED] fix(browser): capture the full visual viewport #7000

New issue

Closed

opened 2026-11-01 21:44:37 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:44:37 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5621
Author: @STDquantum
Created: 10/20/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: fix/browser-visual-viewport-screenshot

📝 Commits (4)

c6fc256 fix(browser): capture the full visual viewport
530f2f5 fix(browser): preserve surface geometry and high-DPI screenshot bounds
1b9f87f chore: merge upstream screenshot identity fixes
6c989e1 fix(browser): reject stale screenshot captures

📊 Changes

6 files changed (+946 additions, -17 deletions)

View changed files

📝 scripts/fixtures/browser-verifier-site.mjs (+7 -0)
➕ scripts/lib/browser-viewport-screenshot-e2e.mjs (+195 -0)
📝 scripts/verify-real-browser.mjs (+7 -0)
📝 src/browser/CdpScreenshot.ts (+153 -17)
📝 tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts (+567 -0)
📝 tests/fixtures/fakeCdpBrowserResults.ts (+17 -0)

📄 Description

Summary

Fixes #5610.

REA could return a cropped screenshot and still describe it as the complete visible viewport. Capture now checks the image against the measured viewport and recovers a truncated surface with an explicit clip. Normal surface captures keep their scrollbars and pixel density.

Problem and expected behavior

On Windows Chrome, a 1280×720 emulated viewport produced a 1264×569 PNG, losing a marker at CSS row 650 despite reporting complete viewport coverage. A screenshot should cover the measured viewport or report why it could not. It must not return an old page region after the viewport changes.

Change and scope

Keep the normal surface PNG when it covers the visual viewport, preserving scrollbars and pixel density. Otherwise, retry once using a fresh CSS viewport clip. Device-pixel metrics supply the coverage lower bound; CSS metrics supply clip coordinates.

Read and validate geometry before and after each capture. If position, dimensions, scale, or pixel density change, return target_changed. Check observed document identity, navigation, and allowed origins after awaits, before issuing another capture. Invalid metrics or insufficient recovery return protocol_error.

This stays within the existing screenshot workflow; no new provider or target authority is introduced.

Contract and boundary impact

Semantic owner: CdpScreenshot, at the CDP capture boundary.
CLI/MCP inputs, output schema, generated catalog, package metadata, and installation: unchanged.
Provider/platform: Chrome-family CDP; tested locally on Windows Chrome.
Evidence: retain the existing PNG identity and document/origin checks, while capturing the requested visible area.
Authority and cleanup: the existing browser attachment owns the extra metrics query. No scrolling, target script evaluation, or emulation override is added.

Expected effects:

Read existing files or captured data.
Launch or attach to a process.
Inject instrumentation or run scripts/code.
Change process memory, registers, files, or configuration.
Contact network services.
Recover protected code or work around protections.
Documentation or usability only; no target interaction.
Not sure yet; investigation or maintainer guidance needed.

The network effect is the existing connection to the caller-selected CDP endpoint.

Evidence and regression coverage

Boundary tests cover stable recovery, CSS/device-pixel units, scrollbar preservation, malformed metrics, and document identity. New cases deliver scope-loss events while metrics are pending and assert that no subsequent screenshot is issued. Scroll, resize, zoom, density changes, and invalid refreshed metrics are also covered.

The real Chrome regression records actual production commands and PNG responses. It asserts that the first image really is undersized and that a clipped retry occurs. Chrome restores the capture session's own metrics during recovery in this external-session fixture; the operation now correctly returns target_changed. The internal recovery PNG is compared pixel-for-pixel with a direct CSS-clip control. A separate stable-viewport capture must succeed with matching dimensions and pixels. Both page scales (1 and 2) pass, including a separate physical-DPR-2 run at 2560×1440.

The real success case does not prove stable cropped recovery; that behavior is covered by wire boundary tests. Existing large-PNG CLI/MCP parity and export checks remain intact.

Observed, derived, and inferred claims remain distinguishable.
Artifact identity, source provenance, and failed attempts remain preserved.
Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

Five focused screenshot, browser lifecycle/document, CLI, and MCP files: 98 tests passed, including 38 screenshot tests.
npm run check: passed.
npm run verify:browser: passed on Windows Chrome 155.0.8059.85, including large-PNG CLI/MCP/export checks and the strengthened viewport regression. Whole-verifier Windows process lineage is unavailable; provider-owned cleanup is checked separately.
Separate physical-DPR-2 production-boundary run: both page scales passed.
An independent agent with no inherited conversation reviewed the production changes and final real-browser helper. It found no demonstrated actionable defect. This was source review, not an independent rerun of the suite.

Compatibility, safety, and release

No schema change or migration is required. macOS/Linux, Edge, mobile viewports, and older Chromium were not tested. Geometry sampling is not atomic: changes after a sample or changes that return to the same values can still escape detection. Rejecting a result cannot undo a capture already in flight.

Normal screenshots add two metrics requests; a cropped surface needs three and at most one extra screenshot. Timing, CPU, and peak process-family memory costs were not measured.

Author readiness

Human owner: @STDquantum

I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
I declare this PR ready for initial maintainer review.

Before merge

This PR addresses a concrete problem or an agreed enhancement.
Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
The PR has one focused outcome and the title follows type(scope): outcome.
Related issue is linked, or the reason for not linking one is stated above.
Tests cover changed observable behavior and meaningful failure paths.
Owning docs, contracts, and generated metadata are updated where needed.
User-visible CLI/MCP changes include representative output.
I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5621 **Author:** [@STDquantum](https://github.com/STDquantum) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/browser-visual-viewport-screenshot` --- ### 📝 Commits (4) - [`c6fc256`](https://github.com/morluto/rea/commit/c6fc2564d7288d71ad49bec066c3cd840b132031) fix(browser): capture the full visual viewport - [`530f2f5`](https://github.com/morluto/rea/commit/530f2f53687ed21cfd2fb65ce6ec0b1c63a56c56) fix(browser): preserve surface geometry and high-DPI screenshot bounds - [`1b9f87f`](https://github.com/morluto/rea/commit/1b9f87f8c44bf684e083e5d4fac04ef09912cc2a) chore: merge upstream screenshot identity fixes - [`6c989e1`](https://github.com/morluto/rea/commit/6c989e15912c659ba9e0f74da2d3433553993c66) fix(browser): reject stale screenshot captures ### 📊 Changes **6 files changed** (+946 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `scripts/fixtures/browser-verifier-site.mjs` (+7 -0) ➕ `scripts/lib/browser-viewport-screenshot-e2e.mjs` (+195 -0) 📝 `scripts/verify-real-browser.mjs` (+7 -0) 📝 `src/browser/CdpScreenshot.ts` (+153 -17) 📝 `tests/boundary/browser/cdpScreenshotDocumentIdentity.test.ts` (+567 -0) 📝 `tests/fixtures/fakeCdpBrowserResults.ts` (+17 -0) </details> ### 📄 Description ## Summary Fixes #5610. REA could return a cropped screenshot and still describe it as the complete visible viewport. Capture now checks the image against the measured viewport and recovers a truncated surface with an explicit clip. Normal surface captures keep their scrollbars and pixel density. ## Problem and expected behavior On Windows Chrome, a 1280×720 emulated viewport produced a 1264×569 PNG, losing a marker at CSS row 650 despite reporting complete viewport coverage. A screenshot should cover the measured viewport or report why it could not. It must not return an old page region after the viewport changes. ## Change and scope Keep the normal surface PNG when it covers the visual viewport, preserving scrollbars and pixel density. Otherwise, retry once using a fresh CSS viewport clip. Device-pixel metrics supply the coverage lower bound; CSS metrics supply clip coordinates. Read and validate geometry before and after each capture. If position, dimensions, scale, or pixel density change, return `target_changed`. Check observed document identity, navigation, and allowed origins after awaits, before issuing another capture. Invalid metrics or insufficient recovery return `protocol_error`. This stays within the existing screenshot workflow; no new provider or target authority is introduced. ## Contract and boundary impact - Semantic owner: `CdpScreenshot`, at the CDP capture boundary. - CLI/MCP inputs, output schema, generated catalog, package metadata, and installation: unchanged. - Provider/platform: Chrome-family CDP; tested locally on Windows Chrome. - Evidence: retain the existing PNG identity and document/origin checks, while capturing the requested visible area. - Authority and cleanup: the existing browser attachment owns the extra metrics query. No scrolling, target script evaluation, or emulation override is added. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [x] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. The network effect is the existing connection to the caller-selected CDP endpoint. ## Evidence and regression coverage Boundary tests cover stable recovery, CSS/device-pixel units, scrollbar preservation, malformed metrics, and document identity. New cases deliver scope-loss events while metrics are pending and assert that no subsequent screenshot is issued. Scroll, resize, zoom, density changes, and invalid refreshed metrics are also covered. The real Chrome regression records actual production commands and PNG responses. It asserts that the first image really is undersized and that a clipped retry occurs. Chrome restores the capture session's own metrics during recovery in this external-session fixture; the operation now correctly returns `target_changed`. The internal recovery PNG is compared pixel-for-pixel with a direct CSS-clip control. A separate stable-viewport capture must succeed with matching dimensions and pixels. Both page scales (1 and 2) pass, including a separate physical-DPR-2 run at 2560×1440. The real success case does not prove stable cropped recovery; that behavior is covered by wire boundary tests. Existing large-PNG CLI/MCP parity and export checks remain intact. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - Five focused screenshot, browser lifecycle/document, CLI, and MCP files: 98 tests passed, including 38 screenshot tests. - `npm run check`: passed. - `npm run verify:browser`: passed on Windows Chrome 155.0.8059.85, including large-PNG CLI/MCP/export checks and the strengthened viewport regression. Whole-verifier Windows process lineage is unavailable; provider-owned cleanup is checked separately. - Separate physical-DPR-2 production-boundary run: both page scales passed. - An independent agent with no inherited conversation reviewed the production changes and final real-browser helper. It found no demonstrated actionable defect. This was source review, not an independent rerun of the suite. ## Compatibility, safety, and release No schema change or migration is required. macOS/Linux, Edge, mobile viewports, and older Chromium were not tested. Geometry sampling is not atomic: changes after a sample or changes that return to the same values can still escape detection. Rejecting a result cannot undo a capture already in flight. Normal screenshots add two metrics requests; a cropped surface needs three and at most one extra screenshot. Timing, CPU, and peak process-family memory costs were not measured. ## Author readiness Human owner: @STDquantum - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-11-01 21:44:37 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-11-03 13:38:43 +00:00

[PR #7000] [MERGED] feat(artifacts): inventory and extract Node.js single executable application blobs #7562

No Branch/Tag specified

main

codex/procedure-reference-stacked

release-please--branches--main--components--rea-agents

release-please--branches--main--components--rea-agents--release-notes

codex/kuna-independent-retry

codex/byte-search-overlay-coverage

codex/open-failure-target-receipt

codex/kuna-xref-evidence

codex/ghidra-ambiguous-procedure-recovery

codex/function-source-bundle

codex/trace-function-integration-prototype

codex/snapshot-source-closure

codex/recorded-evidence-array-pages

codex/evidence-recovery-redesign

codex/trace-feature-address-scope

codex/call-discovery-scope

codex/ghidra-literal-candidate-evidence

codex/decompile-directory-independent-retry

codex/retry-provenance-base

codex/value-flow-capability-experiment

codex/ghidra-containing-instruction

cursor/readme-discord-button-ef9f

dependabot/github_actions/actions/setup-node-7.1.0

dependabot/github_actions/actions/upload-artifact-7.0.2

dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df

codex/kuna-1989

fix/8559-native-ui-fixture-ownership

fix/8555-go-verifier-mcp-ownership

codex/provider-capability-recovery

fix/8642-rizin-target-stdin

codex/ghidra-memory-effect-scope

codex/ghidra-annotation-entry-selector

codex/ghidra-readonly-recovery

codex/ghidra-regex-verifier-recovery

codex/evidence-discovery-view-guidance

fix/8545-bulk-append-overflow

fix/8428-navigation-refusal-alternatives

codex/address-context-recovery

codex/matching-member-limitations

codex/unknown-scope-contract

codex/evidence-view-guidance

feat/8373-native-trace-views

codex/ghidra-snapshot-verifier-binding

codex/elf-export-visibility

codex/evidence-view-recovery

codex/native-reference-cli-help

codex/provider-candidate-observation-scope

codex/kuna-session-verification

codex/ghidra-switch-lifetime-guidance

codex/pseudocode-paging-discovery

codex/clarify-evidence-view-support

codex/kuna-xrefs-selector-recovery

codex/context-capacity-recovery

codex/evidence-closure-large-links

codex/same-function-evidence-identity

codex/ghidra-verifier-inspected-jdk

codex/audit-guided-workflows

codex/crash-prompt-retained-dossiers

codex/analysis-view-error-recovery

codex/kuna-verifier-target-selection

codex/ghidra-selected-project-call-coverage

codex/docs-native-analysis-scope

codex/ghidra-java-socket-boundary

codex/ghidra-retained-snapshot-verifier

codex/ghidra-search-inventory-facts

fix/8284-zero-argument-parameter-bindings

fix/8198-ui-action-handler-offset

fix/8257-elf-entry-label-identity

fix/8304-deferred-output-schema-projection

fix/8277-call-path-computed-target-uncertainty

fix/pr-8089-conflicts

fix/ci-static-duplicate-export

dependabot/npm_and_yarn/lint-staged-17.6.0

dependabot/github_actions/actions/download-artifact-8.0.2

dependabot/npm_and_yarn/write-file-atomic-8.0.0

dependabot/npm_and_yarn/canonicalize-5.1.0

dependabot/github_actions/actions/cache/restore-6.1.0

dependabot/npm_and_yarn/toon-format/toon-4.4.0

dependabot/github_actions/actions/deploy-pages-5.0.1

codex/review-fixes-pr-2403

codex/review-fixes-pr-2400

codex/process-terminal-width

codex/test-brittleness-cleanup

verify/7167-browser-connect-macos

fix/7167-browser-connect

feat/native-matching-allowance-setting

feat/browser-scenario-dry-run

test/managed-caller-parameters-20261024

codex/parser-fortythird-boundaries

fix/6926-pinvoke-platform-decorations-20261023

fix/6889-har-body-encoding-20261023

fix/6888-sqlite-schema-budget-20261023

fix/dependency-security-gates-6708

cursor/evidence-overwrite-rebase-b4ac

feat/4057-verify-native-exports

fix/windows-acl-observer-overhead-20261022

cursor/erlang-beam-restack-4476

cursor/pe-certificate-review-bf32

fix/6116-javascript-application-fs-errors

fix/6061-unmapped-runtime-script-unknown

feat/browser-scenario-summary

fix/pe-certificates

codex/verify-3407

cursor/rebase-5699

cursor/rebase-5352

cursor/rebase-5600

cursor/fix-cli-schema-omission-10a8

codex/audit-hopper-shutdown-reasons-20261021

fix/demangle-swift-omitted-record

fix/nib-boolean-value-types

cursor/cancellation-partial-observation-a5ac

fix/ib-object-limit-reasons

fix/electron-fuse-limit-advice

fix/kuna-doctor-dangling-cache

fix/fixed-budget-refusal-advice

fix/js-ipc-listener-dedup

fix/js-return-member-provenance

fix/dmg-integrity-retry-advice

fix/ida-doctor-readiness

fix/kuna-version-probe-output-drain

fix/legacy-swift-runtime-name-matching

fix/dylib-lazy-load-commands

fix/browser-scenario-startup-cancel

fix/swift-nested-punycode-classification

fix/compare-unselected-scopes

fix/objc-method-budget-coverage

fix/dmg-mounted-root-observations

audit/ci-tests-20261019-round2

release/6.7.0

fix/wabt-cleanup-retry-resolution

fix/electron-fuse-elf-pe-architecture

fix/native-plist-descriptor-ownership

fix/kuna-caller-cleanup-ownership

experiment/atomic-codemode-20261016

review/first-contributor-3776

fix/call-resolution-full-read-cycles

fix/member-mutation-selection-repeat

experiment/atomic-re-tools-20261015

perf/member-mutation-lazy-origins

perf/static-network-mutation-index

fix/hopper-startup-lifecycle

audit/3050-windows-proof-20261015

feat/windows-window-capture-2183

audit/3049-windows-proof-20261015

audit/3735-macos-fixtures-20261015

fix/batch-decompile-null-pseudocode

fix/kuna-inventory-honors-jobs

experiment/browser-codemode-tool-design-20261015

fix/hopper-clean-runtime-argv

codex/review-2049-27f1b367

review-fixes/pr-2787-routing

fix/3360-scoped-this-emitters

fix/3367-replaced-global-effects

fix/3838-compact-any-value-items

test/hopper-download-probe-20261015

codex/windows-runtime-creation-red-green-20261015

codex/windows-readonly-root-red-green-20261015

codex/windows-root-share-red-green-20261015

codex/exp-1685-win-mcp-startup

codex/bug-sweep-20261015

investigate/2190-windows-package-phases

investigate/3543-macos-cli-deadline

perf/3281-reverse-tools-feedback-quality

fix/3406-hopper-doctor-fixture

fix/3341-wrapper-require-test-context

fix/3301-owned-uninstall-fixtures

fix/3164-compiler-input-ownership

fix/pcap-cleanup-stdout-newline-20261014

perf/interface-builder-summary

codex/review-fixes-pr-1977

fix/ghidra-effective-jvm-platform

fix/docs-turkish-rust-link-20261013

fix/main-maintenance-ci-20261010

fix/recover-binary-session-process-effects

codex/review-fixes-pr-2457

codex/ci-required-cancellation-gate

fix/main-format-baseline-20261013

fix/setup-preserve-entry-fields

cursor/restore-main-checks-1ffc

fix/ghidra-bridge-hashmap-import

codex/shared-ci-jadx-json-default-20261013

codex/shared-ci-ghidra-test-groups-20261013

codex/shared-ci-java-fixture-format-20261013

codex/fix-intrinsic-invocation-boundaries

test/release-preflight-reusable-jobs

test/js-parameter-provenance-expectation

fix/linux-hopper-verification-current

test/2419-ghidra-elf-probe-size

followup/pr-1544-native-ida

codex/fold-pr-2230-contribution

docs/readme-responsible-use

fix/issue-2064

fix/issue-2050

fix/issue-2053

fix/issue-1968

fix/issue-1945

experiment/codemode-bridge-20261011

fix/tool-effects-negative-wording-1904-20261012

fix/1842-electron-interop-provenance

feat/recover-javascript-multi-input

refactor/website-i18n-prep

fix/nativeaot-pe-virtual-extent

fix/browser-verifier-ci-hang

fix/pe-resources-input-selection

docs/beginner-friendly-guides

docs/beginner-setup-guide

fix/javascript-analysis-worker-1563

fix/1649-ghidra-duplicate-names

fix/javascript-export-keys-integration-1369

test/maintenance-boundary-contracts-20261011

review/javascript-export-keys-1369

review/process-live-progress-1483

test/javascript-1495-growth-ratio

fix/ci-escape-timing

docs/normalized-terminal-geometry-1450

release/6.3.0

archive/release-6.3.0-pr1381

release/6.2.0

fix/electron-preload-dynamic-override

fix/javascript-self-referential-bundler-edges

release/6.1.0

cursor/grok-client-cherry-pick-0b56

feat/signature-posture

feat/dyld-shared-cache

feat/artifact-integrity-policy

feat/pkg-inventory

release/6.0.0

chore/sync-release-5.0.0

release/5.0.0

cursor/cloud-agent-node-787e

fix/javascript-xhr-open-endpoints

review/pr-711-realpath-fallback-wording

cleanup/replay-confinement

codex/test-suite-performance

codex/issue-foundations

codex/address-open-issues-2026-07-20

agent/javascript-vite-rollup-esbuild-adapters

agent/process-cleanup

agent/triage-integration

agent/unknown-commands-registry

feat/mcp-identity-metadata

morlvps/issue_cleanup

codex/installer-redesign

morl/roadmap-investigation-core

morl/roadmap-investigation-docs

release-please--branches--main--components--rea

rea-agents-6.8.0

rea-agents-6.7.0

rea-agents-6.6.0

experiment/atomic-codemode-wait-runtime-20261016

rea-agents-6.5.0

rea-agents-6.4.0

rea-agents-6.3.0

rea-agents-6.2.0

rea-agents-6.1.0

rea-agents-6.0.0

rea-agents-5.0.0

rea-agents-4.1.0

rea-agents-4.0.1

rea-agents-4.0.0

rea-agents-3.2.1

rea-agents-3.2.0

rea-agents-3.1.0

rea-agents-3.0.0

rea-agents-2.7.0

rea-agents-2.6.0

rea-agents-2.5.1

rea-agents-2.5.0

rea-agents-2.4.0

rea-agents-2.3.0

rea-agents-2.2.0

rea-agents-2.1.0

rea-agents-2.0.0

rea-agents-1.7.0

rea-agents-1.6.0

rea-agents-1.5.0

rea-agents-1.4.0

rea-agents-1.3.0

rea-agents-1.2.0

rea-agents-1.1.0

rea-agents-1.0.0

rea-agents-0.5.0

rea-agents-0.4.0

rea-agents-0.3.0

rea-0.2.1

rea-0.2.0

Labels

Clear labels

Mirrored from GitHub Pull Request

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#7000

Reference in a new issue

Repository

morluto/rea

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns