Community
Participate
Working Groups
a) Remove the experimental description => Why do we need this method b) Remove the method
a) -> no, we don't need the method. It was part of an experiment to optimize performance, see bug 209097. When the changes for that bug caused test failures, they were rolled back incompletely. b) This would have been a good thing before the API freeze, but we cannot do that anymore. c) I think the only option we have is to mark the method as deprecated. Should we do c) for 3.4 or 3.5? I am voting for 3.5...
What about methods like internalAdd(Widget, Object, Object[]), internalRefresh(Widget, Object, boolean, boolean), and internalRemove(Object[])? Should their experimental description also be removed while we're at it?
Can we get a target milestone set on this so it's not forgotten?
Marked getChildren(Widget, Object[]) as deprecated. About the methods mentioned in comment #2, we should discuss that as part of bug 232268.
Verified by code inspection using I20081028-0100