Allow a payment handler to request a larger initial window size

Open

#1,075 opened on Aug 24, 2026 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Active
Tech stack: html
Domain: api, mobile-dev, payments

Research direction

Start at PaymentRequestEvent.openWindow() and the payment app manifest fields named in the issue: name, icons, and serviceworker. Compare the proposed manifest hint with an openWindow() parameter, including how browser-specific constraints may apply. Done means the specification has one agreed mechanism for requesting a larger initial presentation.

Written by the indexing model from the issue text.

Description

Problem

When a web-based payment handler opens a window via PaymentRequestEvent.openWindow(), the
browser is free to choose how much of the screen that window occupies. In practice, on Android,
this window opens at a partial (half-screen) height by default, requiring the buyer to manually
expand it before they can see or interact with the full payment app UI. The spec currently has no
mechanism for a payment handler to express a preference for a larger initial presentation.

Proposed solution

Add an optional way for a web-based payment handler to indicate it needs a larger initial
presentation, for example:

A field in the payment app manifest (alongside name, icons, serviceworker) indicating a
preferred initial size or display mode, or
A parameter on openWindow() (or a new method) allowing the handler to request full-height
presentation from the start.

As with other capabilities in this spec, the browser could still ignore the hint or apply
implementation-specific constraints — this would just give payment handlers a way to express
intent.

Screenshots

_{The payment handler window opened at its default partial (half-screen) height.}

_{The same window after the buyer manually drags it open to full height.}

Dominant language: HTML
Stars: 510
Forks: 139
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] [Connector-V2] [Http] A streaming Http source never completes a checkpoint: poll_interval_millis is waited out holding the checkpoint lock Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

apache/seatunnel#12411 · Opened Sep 20, 2026
wafv2: TagResource/UntagResource don't enforce the 50-tag limit or key/value length limits Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

floci-io/floci#4035 · Opened Sep 20, 2026
[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
popularity.exclude_admin does not work for admin2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

getgrav/grav-plugin-api#45 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026

More Backend & API Design issues