Bug 274583
| Summary: | Show an error with the given URL when an iframe content is blocked | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Milan Crha <mcrha> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bugs-noreply, kdwkleung, mcatanzaro, webkit-bug-importer |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Milan Crha
Coming from Epiphany's https://gitlab.gnome.org/GNOME/epiphany/-/issues/2354
There are still pages which cross-reference content in iframe. It would be nice to make it easier to open an iframe link in a new tab when such blocking happens by showing an error in the iframe instead of an empty place.
Try for example:
https://finance.yahoo.com/sec-filing/TSLA/0001628280-24-017503_1318605?nn=1
The white rectangle shows nothing, while the iframe references:
https://cdn.yahoofinance.com/prod/sec-filings/0001318605/000162828024017503/tsla-20240331.htm
An error message in the iframe could be anything like:
Cannot open https://cdn.yahoofinance.com/prod/sec-filings/0001318605/000162828024017503/tsla-20240331.htm
due to site cross-reference.
Bonus points if the link is clickable.
For example duck-duck-go browser on Android does show an error in the iframe, with the link as well. Firefox also shows an error page, with a button "Open Site in New Window".
This is with epiphany-46.0-2.fc40.x86_64 and earlier version(s) and webkitgtk6.0-2.44.1-1.fc40.x86_64.
I tried also with the MiniBrowser (note of added backslash in front of the `?`):
$ /usr/libexec/webkitgtk-6.0/MiniBrowser https://finance.yahoo.com/sec-filing/TSLA/0001628280-24-017503_1318605\?nn=1
and the outcome is the same, the iframe is empty here. Maybe related, maybe not, I'm asked about cookies before the page loads. I chose "Reject All".
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
(In reply to Milan Crha from comment #0)
> Maybe related, maybe
> not, I'm asked about cookies before the page loads. I chose "Reject All".
I don't see any cookie prompt. Likely that explains why it works for me and not for you.
Kdwk
I am not able to reproduce this bug. The iframe content loads fine for me. There was not any cookie prompt.