Re: [whatwg/webidl] Defining AbstractModuleSource intrinsic inheritance (Issue #1322)

About when prose text "overrides" happens, I think it's nice to have something like "run an interface-specific configuration algorithm" in the imperative realm-initializing algorithms in Web IDL, and let each spec define "run an interface-specific configuration algorithm". This way has already been used in several places, right?

Just as a random idea; It might make sense and be helpful to have an extended attribute like [InterfaceSpecificConfiguration] in order to indicate that the interface has its own unique prose text "overrides". For example, we can use the extended attribute to cross-check whether we appropriately hard-code the behavior.

I'm skeptical about getting rid of hard-coded behaviors even if [IntrinsicHeritage] were introduced (e.g. Location's valueOf, HTMLAllCollection's [[Call]]). I don't think it will be helpful in case of Chromium. However, I don't have a strong objection especially when it will be very helpful for other people and/or projects. The concern about [IntrinsicParent] + [IntrinsicPrototypeParent] will remain, though.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/issues/1322#issuecomment-1596583111
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/issues/1322/1596583111@github.com>

Received on Monday, 19 June 2023 06:25:46 UTC