When generating DOM bindings, if a property is feature-enabled, that property is generated with condition guards around it. This means that that property might not be present in a build that disables that feature. This leads to inconsistent ABI, which is unwanted. Instead of that, all the properties should be present, but when trying to get (or set if writable) the value of a feature-dependent property, a warning should be emitted if the feature was not enabled at compile time. Similarly, if the complete DOM object is feature-dependent, all the properties should still be present but getting or setting the value should throw a warning if that feature was not enabled at compile time.
Created attachment 139215 [details] Patch
Comment on attachment 139215 [details] Patch Clearing flags on attachment: 139215 Committed r115442: <http://trac.webkit.org/changeset/115442>
All reviewed patches have been landed. Closing bug.