Bug 188544 - Synchronously defined custom elements don't get foster-parented
Summary: Synchronously defined custom elements don't get foster-parented
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks: 154907
  Show dependency tree / graph
 
Reported: 2018-08-14 00:08 PDT by Ryosuke Niwa
Modified: 2022-08-10 10:54 PDT (History)
9 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 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).
Comment 1 Ahmad Saleem 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?
Comment 2 Ryosuke Niwa 2022-08-09 23:59:26 PDT 
This is still broken with respect to custom elements.
Comment 3 Radar WebKit Bug Importer 2022-08-10 10:54:55 PDT 
<rdar://problem/98460010>