Identify which surface scrolls
Scroll the main page and then the inner panel before capturing. Observe which content changes. Full-page capture follows the main document, while an internal panel contributes the content currently visible inside it.
An embedded frame or virtualised table may render only a subset of its data. A screenshot records the page state; it does not export all rows, hidden records or protected embedded content. Use a legitimate native data export when complete underlying data is needed.
Prepare the panel’s visible state
- Move the panel to the required section.
- Make its heading and relevant rows visible.
- Capture the visible area or a deliberate crop with context.
- For several panel states, capture and label each separately, reviewing any overlap.
Keep evidence of scope
Retain the panel title and the row or message range. If the scroll position matters, explain it in the accompanying note rather than adding a claim that the image contains the whole dataset. A full-page image can provide surrounding layout as a separate companion.
Choose the next step from the actual result
A panel may show a scrollbar, pagination controls or a virtualised row range. Note which mechanism applies. Page height alone does not describe panel scope. A visible-area capture is often easier to audit because the panel heading and currently shown items can be reviewed together. If an individual message or record is the purpose, retain its identifying label while excluding unrelated private content.
Do not move the panel while a capture runs. Position it first, wait for that state to render, then capture. If the panel updates frequently, identify the actual range present in the saved file. Prepare another state as a separate capture. This deliberate procedure supports a visible-state record and does not promise extraction of records not rendered by the original application.
A worked example
A dashboard displays twenty visible rows inside a panel with two hundred records. The full-page image shows those twenty rows and the dashboard layout. To document row 84, position the panel there and capture its visible state. To obtain all two hundred records, use the dashboard’s authorised export; the screenshot workflow is not that export.
Add your observations. This template processes no files and sends no report.
Check the result
If something is wrong
| Observation | Next step |
|---|---|
| Only some rows captured | This can be the panel’s visible state; position and capture the needed range separately. |
| Embedded content blank | Check the original frame and restrictions; capture cannot bypass access. |
| Panel title cropped away | Widen the crop or add clear context beside the shared image. |
Common questions
Does Full page scroll every panel?
The main-page workflow does not promise independent exhaustive scrolling of every nested panel.
Can it export hidden table rows?
No. Use the source application’s legitimate data export when the underlying dataset is needed.