This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
HTML currently has [OverrideBuiltins] partial interface Document { ... }, which is invalid because you can't have extended attributes on a partial interface. But DOM4 can't add [OverrideBuiltins] to the actual Document interface definition, because that defines no getter. Suggested resolution: allow [OverrideBuiltins] on partial interfaces, and say it has the same effect as if it was specified on the original interface. So the partial interface can add that extended attribute too, not just members.
By just restricting it to the interface or partial interface that has the getter, we can neatly solve the problem of it being unclear which interface should have it.
The non-localised effects of extended attributes on partial interface definitions is exactly what I was trying to avoid with the current spec restrictions. Ian's comment 1 suggestion does neatly get around that problem. (An alternative would be to write in HTML [NoInterfaceObject,OverrideBuiltins] interface DocumentProperties { getter ...; }; Document implements DocumentProperties; .)
I've done comment 1. http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.421;r2=1.422;f=h Aryeh, let me know if this change is satisfactory, thanks.
AFAICT, the grammar still doesn't allow extended attributes on partial interfaces, although the prose now does.
You were right. I fixed this yesterday as part of the callback edit.
Oh, I misread. Never mind me. Updated WebIDLParser.js and idlharness.js: https://github.com/ayg/webidl.js/commit/ebed0073 http://dvcs.w3.org/hg/html/rev/c0952a1118d7