What this means
The recording did not identify a specific actionable control. After the window moved or resized, the recalculated point fell into non-client window chrome, where it could close, minimize, maximize, move, or resize the window. Offisen blocks the click.
What to do
- Move and resize the target window roughly to the position and size used during recording.
- Retry playback.
- If the problem continues, record the step again while clicking directly on a specific button, field, menu item, or other control.
- Avoid using a blank window area as the target when a specific control is available.
Why this can happen
- The target window moved or changed size.
- The click was recorded against the whole window or another generic container.
- Proportional coordinate adjustment placed the point on the title bar, caption controls, or resize border.
- The window could not confirm that the point belongs to its client area.
Example
A click recorded against a large window is replayed after the window becomes smaller. The scaled point lands near the Close button, so Offisen blocks it instead of risking closing the application.
Diagnostic details
| Code | OFS-1808 |
|---|---|
| Symbol | GenericContainerChromeTargetBlocked |
| Domain | Pointer and mouse |
| Layer | Target identification |
| Phase | Playback |
| Severity | Blocking error |
| Retryable | Yes |
| Privacy | Safe support context |
| Safety policy | Block before pointer input |
If the problem continues
If the click is clearly on a specific control and the error repeats, copy the report. It contains geometry and hit-test metadata, but not element names, window titles, or screenshots.
Include the error code, correlation ID, timestamp, Offisen version, target application when relevant, and a short description of what happened. Review the report before sharing it and remove anything you do not want to send.
Contact [email protected].