Configuration options for features that are enabled by default should be removed if the feature doesn't introduce dependencies and is considered stable.
Created attachment 164418 [details] Patch
Comment on attachment 164418 [details] Patch Great!
Comment on attachment 164418 [details] Patch Clearing flags on attachment: 164418 Committed r128776: <http://trac.webkit.org/changeset/128776>
All reviewed patches have been landed. Closing bug.
I see that this patch put DOM MutationObservers in the "unstable features" bucket. Can you explain a bit of the background for that? I ask because I'd like to remove the ENABLE_MUTATION_OBSERVERS #define, since it's been enabled by default everywhere for awhile (and seems to be shipping in several WebKit-based browsers, including Safari and Chrome).
(In reply to comment #5) > I see that this patch put DOM MutationObservers in the "unstable features" bucket. Can you explain a bit of the background for that? I ask because I'd like to remove the ENABLE_MUTATION_OBSERVERS #define, since it's been enabled by default everywhere for awhile (and seems to be shipping in several WebKit-based browsers, including Safari and Chrome). It probably just wasn't turned on for stable releases as an oversight. If it's stable enough to ship, feel free to just remove the option, I'd say.
(In reply to comment #6) > (In reply to comment #5) > > I see that this patch put DOM MutationObservers in the "unstable features" bucket. Can you explain a bit of the background for that? I ask because I'd like to remove the ENABLE_MUTATION_OBSERVERS #define, since it's been enabled by default everywhere for awhile (and seems to be shipping in several WebKit-based browsers, including Safari and Chrome). > > It probably just wasn't turned on for stable releases as an oversight. If it's stable enough to ship, feel free to just remove the option, I'd say. That's the case, GTK port shouldn't pose any obstacles for removing this define, so proceed at will.