Comment #41 on issue 266 by [email protected]: Chrome uses Windows' proxy
settings
http://code.google.com/p/chromium/issues/detail?id=266
Actually the best way to vote for this feature is to star this issue.
There are several nice tutorials about how to write a PAC file. You can
find some
here:
http://jcurnow.home.comcast.net/~jcurnow/WritingEffectivePACFiles.html
http://nscsysop.hypermart.net/proxypac.html
Wikipedia also provides a nice starting point with a good general
introduction.
http://en.wikipedia.org/wiki/Proxy_auto-config
The Chromium team is very open to new engineers. Pawal was our first about
a month
ago, he is a CS student in Poland who has contributed many excellent
patches. You
can read about the process of becoming a committer at
http://dev.chromium.org/getting-involved/become-a-committer
However, you don't need to be a committer to submit patches. Anyone can
submit a
patch but you need a committer to review and commit it for you. You should
expect
any patch to go through the same rigorous code reviews as any work.
Personally, I
find the code reviews to be an excellent way to learn and improve.
Of course, you could write up a tool that helps people generate the PAC
file they
want. This application would benefit all browsers. You could write the
application
in any programming language you want (unlike Chromium code) and it could
even be
dynamic. There are lots of ways to skin this cat.
--
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
-~----------~----~----~----~------~----~------~--~---
