[Webkit-unassigned] [Bug 117488] Consider atomicizing inline scripts before execution

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 7 10:00:06 PDT 2023


--- Comment #2 from Darin Adler <darin at apple.com> ---
This change is a peculiar way to accomplish this. The rationale is specific to script and style elements, but the change is in a general purpose function that is not specific to script and style elements. Maybe there is benefit to doing this as a side effect any time any code calls childTextContent, but it’s a strange choice to have this operation have an unrelated side effect without even changing its name.

The idea itself seems likely sound, but my first choice given this problem statement would be to atomize them during the parsing process, not just before execution. The memory cost takes effect as soon as they are parsed and is paid even if they are never executed. Atomizing each individual text node’s text is not related to concatenating them all into a single large string.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230707/02f0b82c/attachment-0001.htm>

More information about the webkit-unassigned mailing list