Add canvas support to pyide

[Copilot]

• Add canvas support to pyide
• Add canvas example to the website pyide documentation
• Fix: after hitting run, the editor no longer receives automatic focus
• Fix: editor is usable after an exception (don't blur activeElement in releaseKeyboardCapture)
• Fix: call pygame.quit() after canvas execution so keyboard event listeners are released even when a Python exception occurs

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyperbook-4fwa	Ready	Preview, Comment	May 15, 2026 10:41am

[mikebarkmin]

@copilot add an example to the website for element pyide.

[Copilot]

@copilot After hitting run the editor should not get automatic focus.

Fixed in a14bca3. Removed the editor?.focus?.() call from releaseKeyboardCapture so the editor no longer steals focus after clicking run (or stop).

[mikebarkmin]

@copilot after an exception I can not type in the code editor

[Copilot]

@copilot after an exception I can not type in the code editor

Fixed in cdbb0b7. The previous fix inadvertently called document.activeElement?.blur?.() which blurred the editor's textarea on exception — leaving the code-input component in a non-interactive state without a re-focus to recover it. Now releaseKeyboardCapture only blurs the canvas element (to release canvas keyboard capture), so the editor remains usable after an exception without auto-focusing it.

[mikebarkmin]

@copilot I was talking about an exception in python:

Loading pygame-ce
Loaded pygame-ce
pygame-ce 2.5.6.dev2 (SDL 2.32.0, Python 3.13.2)
Traceback (most recent call last):
File "", line 29, in
File "/lib/python313.zip/pyodide/webloop.py", line 961, in _run
return loop.run_until_complete(main)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
File "/lib/python313.zip/pyodide/webloop.py", line 369, in run_until_complete
return run_sync(future)
File "", line 22, in run_game
NameError: name 'sys' is not defined. Did you forget to import 'sys'?

For this code:

import pygame
import asyncio

async def run_game():
fps = 60
pygame.init()
screen = pygame.display.set_mode((400, 300))
r = 0
g = 0
b = 0

while True:
    for event in pygame.event.get():
        if event.type == pygame.KEYDOWN:
            if event.key == pygame.K_r:
                r = (r + 50) % 256
            elif event.key == pygame.K_g:
                g = (g + 50) % 256
            elif event.key == pygame.K_b:
                b = (b + 50) % 256
            elif event.key == pygame.K_ESCAPE:
                sys.exit()
        elif event.type == pygame.QUIT:
            return
    screen.fill((r, g, b))
    pygame.display.flip()
    await asyncio.sleep(1 / fps)

asyncio.run(run_game())

this happens in pyide.md

[Copilot]

@copilot I was talking about an exception in python:

Loading pygame-ce
...

Fixed in 092751e (cleaned up in 3904fd3). When a Python/pygame-ce exception occurs, pygame.quit() is never reached in the user's code, so pygame's keyboard event listeners remain registered on the canvas element and block typing in the editor. The fix adds a cleanup step in the finally block of executeScript that calls pygame.quit() via pyodide whenever canvas execution ends — whether the script succeeded or threw a Python exception.