Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)

Just some field notes on implementation complexity (not an implementer but merely a student of implementations):

All browsers do "string interning" of attribute names. Some of this work would need to be reversed for this (this may result in more heap allocations which would also degrade performance) or delicately authored around (this would make for very complex changes and limit exactly how plausible this would be). So it's _very_ complicated change to make for engines. It touches lots of parts of the codebase and in many places that are optimized intensively to improve performance. It may regress performance, even in the cases where the case-sensitive attribute name is not retrieved (as it still needs to be stored).

So I think there's a very high bar of value required for this change to be deemed high enough priority for browsers to take on the engineering challenge. I would imagine there are mechanisms which could alleviate the general problem while being more palatable (e.g. DOM parts).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1076#issuecomment-2409155136
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1076/2409155136@github.com>