Bug 188544

Summary:	Synchronously defined custom elements don't get foster-parented
Product:	WebKit	Reporter:	Ryosuke Niwa <rniwa>
Component:	DOM	Assignee:	Nobody <webkit-unassigned>
Status:	NEW
Severity:	Normal	CC:	ahmad.saleem792, annevk, ap, bfulgham, cdumez, eoconnor, fred.wang, rniwa, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified
Bug Depends on:
Bug Blocks:	154907

Ryosuke Niwa

Reported 2018-08-14 00:08:57 PDT

Apparently, I unintentionally disabled foster parenting for synchronously defined custom elements. On one hand, this doesn't match the spec. On the other hand, being able to define custom elements anywhere seems useful especially given there doesn't seem to be any compact issues (given WebKit has been shipping this behavior for two years).

Attachments
Add attachment proposed patch, testcase, etc.

Ahmad Saleem

Comment 1 2022-08-09 13:42:43 PDT

rniwa@webkit.org - Safari is passing foster parenting test on WPT: https://wpt.fyi/results/html/syntax/parsing/template/additions-to-foster-parenting?label=master&label=experimental&aligned&view=subtest&q=foster%20parent Is this required or it is different issue and WPT does not have coverage for this?

Ryosuke Niwa

Comment 2 2022-08-09 23:59:26 PDT

This is still broken with respect to custom elements.

Radar WebKit Bug Importer

Comment 3 2022-08-10 10:54:55 PDT

<rdar://problem/98460010>

Note You need to log in before you can comment on or make changes to this bug.