Blake Ross wrote: > First of all, he is the default assignee for that component, not the > module owner. (Yeah, this is a confusing distinction. Mozilla.org is > working on cleaning it up, and there's an updated module owner list, but > I can't find the url right now...) It is likely, furthermore, that this > component is going away.
What do you mean by it is likely that this component is going away? Do you mean that they won't work on these usability improvements after all? If so, why? I can understand (or should I say, I have accepted the fact) that this doesn't have high priority, but dropping it alltogether? I'm disappointed. / David
