Skip to content

[filter-effects-1] Document Clickjacking Attacks#13846

Open
arichiv wants to merge 3 commits into
w3c:mainfrom
arichiv:patch-2
Open

[filter-effects-1] Document Clickjacking Attacks#13846
arichiv wants to merge 3 commits into
w3c:mainfrom
arichiv:patch-2

Conversation

@arichiv
Copy link
Copy Markdown
Member

@arichiv arichiv commented Apr 28, 2026

This formalizes the proposal here: https://chromestatus.com/feature/5117170452398080

Comment thread filter-effects-1/Overview.bs Outdated
Comment thread filter-effects-1/Overview.bs
Comment thread filter-effects-1/Overview.bs Outdated
@arichiv
Copy link
Copy Markdown
Member Author

arichiv commented May 6, 2026

Chrome is currently discussing whether all iframes, or just iframes that are cross-origin with their parent, should have the SVG filter un-applied. Soliciting feedback on that here.

@rebane2001
Copy link
Copy Markdown

From a security perspective, same-origin frames allowing filters would be on-par with how the rest of the restrictions with frames work. The concerns would probably be additional complexity in the case of nested frames, and confusing behavior where filters work on one frame but not another. I personally like the idea of still being able to use filters on my own frames :).

@tabatkins
Copy link
Copy Markdown
Member

Yeah, there's no good reason to disallow filters on same-origin iframes. A same-origin iframe is not remotely a security boundary.

Expanded explanation on the risks of applying SVG filters to cross-origin iframes.
@arichiv arichiv requested a review from tabatkins May 16, 2026 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants