Updates:
Status: Duplicate
Mergedinto: 266
Comment #5 on issue 7792 by [email protected]: Chrome needs its own proxy
configuration
http://code.google.com/p/chromium/issues/detail?id=7792
This is a new argument to the same request but I don't think having two
bugs adds
value. I want to keep this conversation in 266 so we only have one place
to look
when we start work on the feature.
I am convinced that we will eventually provide a mechanism for this.
However, the
bug remains Won't Fix so people don't get the impression that we are
currently
working on it or that they will see it soon. Our efforts in the 2.x branch
leave us
no time to work on this feature.
I read every comment to 266. It is not forgotten or ignored. The reality
is that
every engineering team needs to have discretion in choosing its workload
for a
release. While this is a very popular issue for some, it is not yet at the
top of
the list as I see it.
Thank you very much for contributing this use case. I will be sure it is
considered
when we begin work on the feature. If you have starred the issue you will
know when
we start work because the status will change.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
