Skip to content

docs(plugins): a swallowed new_page failure keeps the failed page - #14

Merged
aaltat merged 1 commit into
MarketSquare:mainfrom
aaltat:docs/plugin-failed-page
Oct 4, 2026
Merged

aaltat merged 1 commit into
MarketSquare:mainfrom
aaltat:docs/plugin-failed-page

Conversation

@aaltat

@aaltat aaltat commented Sep 26, 2026

Copy link
Copy Markdown
Member

Adds a short aside to Extending → Python plugins for plugin authors.

After MarketSquare/robotframework-browser#5273 (fixes MarketSquare/robotframework-browser#5261), a failing New Page keeps the failed page open and active until failure handling is done, so the failure screenshot shows the right page. For a plugin keyword that calls self.library.new_page(...), that means the failed page stays active until the plugin keyword returns. A plugin that catches the error and carries on has to switch back itself; the note shows how with switch_page.

Only the plugin page changes; the New Page keyword docs are already updated in the library.

Merge after the Browser release that includes #5273.

🤖 Generated with Claude Code

A plugin keyword that catches a failing self.library.new_page(...) keeps
running against the failed page until it returns. Show how to switch
back to the previous page.

Refs MarketSquare/robotframework-browser#5261

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aaltat
aaltat merged commit 41d0df6 into MarketSquare:main Oct 4, 2026
1 check passed
@aaltat
aaltat deleted the docs/plugin-failed-page branch October 4, 2026 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Failing New Page closes the page before run_on_failure, so the failure screenshot is missing or shows a different page

1 participant