1953738 - Credit card not filled in leicesterhospitalscharity.org.uk donation form (using stripe with an iframe for each field)

Status: NEW

(Toolkit :: Form Autofill, defect, P3)

Description

[:Gijs (he/him)]

STR:

0. have at least one payment card saved
1. go to https://leicesterhospitalscharity.org.uk/
2. on the big form on the homepage pick any amount and click "donate now"
3. scroll down to the "Donate with Donate via Credit or Debit Card" section
4. click in the "card number" field

ER:
autofill dropdown

AR:
no autofill dropdown

This is using Stripe and using a frame (from https://js.stripe.com/) for each field. The input field inside the form looks like:

<input class="InputElement is-empty Input Input--empty" autocomplete="cc-number" autocorrect="off" spellcheck="false" type="text" name="cardnumber" data-elements-stable-field-name="cardNumber" aria-required="true" inputmode="numeric" aria-label="Credit or debit card number" placeholder="Card Number" aria-invalid="false" tabindex="0" value="">

and the form:

<form class="ElementsApp is-empty" style="" dir="ltr"></form>

Comment 1

[:Gijs (he/him)]

This also affects https://bacacharity.org.uk/?form=donate

Steps there:

0. have at least one payment card saved
1. go to https://bacacharity.org.uk/?form=donate
2. on the form on the homepage pick any amount and click "Donate"
3. Click "keep my one-off gift" if prompted
4. Enter a first name and last name of at least two letters, and a valid email address
5. tick "donate anonymously" and "read our privacy policy"
6. click "No thanks" for gift aid
7. click in the card field with the "1234..." placeholder or the expiration field

They seem to be using a really big iframe for most of the page and then separate iframes again for the stripe elements.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:dimi, could you have a look please?

For more information, please visit BugBot documentation.

Comment 3

[Dimi Lee [:dimi]]

gihs, thank you for filing the issue!
The website uses nested <iframe>, which we currently don't support. The reason we don't support nested <iframe> is that when we initially implemented <iframe> support, we didn't encounter any examples requiring it, so we chose to keep the solution simple.
I will work on this issue.

Comment 4

[Alin Ilea, Desktop Test Engineering]

Attachment: 2026-01-16_14h32_43.mp4

Just verified the issues in the latest Nightly 149.0a1(build id:20260116093521 ) after bug 1966600 fix, but both issues(from the description and comment 1), are still reproducible in the same way they are described above.