[dependabot]

Updates the requirements on playwright to permit the latest version.
Updates playwright to 1.64.0

Release notes

Sourced from playwright's releases.

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

browser = chromium.launch(args=["--enable-features=WebMCP"])
page = browser.new_page()
page.goto("https://example.com")
for tool in page.webmcp.tools():
print(tool["name"], tool["description"])
result = page.webmcp.call_tool("add", {"a": 2, "b": 40})
print(result["content"][0]["text"])  # "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

page.screencast.start(path="video.webm", size={"width": 1920, "height": 1080}, fps=60)
page.screencast.show_actions(
    style={
        "point": "width: 20px; height: 20px; border-radius: 50%; background: red",
        "highlight": "outline: 2px solid [#333](https://github.com/microsoft/playwright-python/issues/333); background: rgba(0, 128, 255, .15)",
        "title": "font-size: 16px",
    }
)

• New record_video_fps option and new fps option in screencast.start(). Firefox and WebKit currently capture up to 25 frames per second.
• New style option takes CSS declarations for the point marker, the target highlight and the action title. It replaces the font_size option, which is now deprecated.
• The cursor stays visible at the last action point, survives navigations and travels along a natural, eased path.
• Videos are encoded with VP9 instead of VP8, which takes less CPU and produces smaller files of the same or better quality.

... (truncated)

Commits

• 387a8a9 cherry-pick(#3252): devops: publish to PyPI from GitHub Actions with trusted ...
• 71d2a17 chore: roll Playwright to v1.64.0 (#3251)
• d566fc5 fix(fetch): JSON-stringify NaN and Infinity string data (#3249)
• 2959d19 docs(skills): add a skill to prepare a release (#3250)
• 5313ac2 fix(network): keep blank values in Request.post_data_json for form bodies (#3...
• 9d8c50f chore(codegen): use alphabetical order in the generated API (#3242)
• 478282f chore(codegen): generate the public TypedDicts from the docs (#3247)
• b8b7155 fix: raise Error instead of assert for user input validation (#3245)
• 1de5d37 fix(network): do not add missing headers when looking them up (#3246)
• 222a2e0 chore(codegen): type _impl_obj in the generated API (#3241)
• Additional commits viewable in compare view

[ARSH871-bot]

Approving fd7acfb. Green CI is not the evidence here, so this is what I checked instead.

Nothing automated uses playwright. It appears in no file under tests/, tools/ or web/. requirements-dev.txt says the suite does not use it, and CI installs requirements.txt only. So this floor affects the hand-run browser checks and nothing else.

Those checks work on 1.63. In a throwaway environment with playwright 1.63.0 (8 October):

• Chromium 153.0.8010.12 launched with no extra browser download.
• It drove the full draft-policy flow on a live dashboard: refused before upload, config uploaded, draft downloaded, unedited draft refused with all 4 decisions listed, and findings still on the built-in policy afterwards.

One thing to know, which does not need changing: a machine still on 1.62 no longer meets this floor. tools/preflight.py checks requirements.txt only, so nothing turns red; run pip install -r requirements-dev.txt --upgrade before the next browser check.