[chromium-dev] Re: Design doc: Background Browser Task

2008-10-28 Thread Brian Rakowski
Drag and drop seems like a clumsy and unfamiliar mechanism for granting this
capability. A modal dialog would be better. We can inject a delay on making
the OK button active if we are worried about clever attacks that get users
to click on an OK that appears underneath the cursor.
-Brian

On Tue, Oct 28, 2008 at 5:55 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote:

>
> Hi all,
>
> Here is a draft of a design doc for Background Browser Task:
>
> http://docs.google.com/View?docid=dd6rm2wb_3fmz8pnnp
>
> Your feedback is appreciated.
>
> Thanks,
>
> Jian
>
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~--~~~~--~~--~--~---



[chromium-dev] Design doc: Background Browser Task

2008-10-28 Thread [EMAIL PROTECTED]

Hi all,

Here is a draft of a design doc for Background Browser Task:

http://docs.google.com/View?docid=dd6rm2wb_3fmz8pnnp

Your feedback is appreciated.

Thanks,

Jian


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~--~~~~--~~--~--~---



[chromium-dev] Re: Building on Ubuntu/hardy AMD64

2008-10-28 Thread Marc-Antoine Ruel

2008/9/3 Graeme Humphries <[EMAIL PROTECTED]>:
> Because hardy's svn client is too old, we can't use the svn snapshot on the
> wiki, so we need to just
> check everything out. This will take hours, as the repo is ~1.4G.

That is definitely an oversight of our part. Needs to be fixed. Just
need to find someone to volunteer to create a new one.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~--~~~~--~~--~--~---



[chromium-dev] Re: avoiding checking into a closed tree with git-cl

2008-10-28 Thread Eric Seidel

That is s awesome Evan.

On Tue, Oct 28, 2008 at 11:11 AM, Evan Martin <[EMAIL PROTECTED]> wrote:
>
> If you're using git-cl, it now can check whether the tree is closed
> automatically.  (Thanks Tony!)
> 1) Pull a new git-cl.
> 2) Run "git cl config" again.  It'll ask you for a tree status URL --
> use http://chromium-status.appspot.com/current .
> 3) Two comands are affected:
> 3a) git cl tree   # prints the tree status
> 3a) git cl dcommit   # checks the tree status before committing
>
> To force a commit on a closed tree (for example, to unbreak the tree),
> use the -f (force) flag to dcommit.
>
> This info has been added to the using-git page on dev.chromium.org as well.
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~--~~~~--~~--~--~---



[chromium-dev] avoiding checking into a closed tree with git-cl

2008-10-28 Thread Evan Martin

If you're using git-cl, it now can check whether the tree is closed
automatically.  (Thanks Tony!)
1) Pull a new git-cl.
2) Run "git cl config" again.  It'll ask you for a tree status URL --
use http://chromium-status.appspot.com/current .
3) Two comands are affected:
3a) git cl tree   # prints the tree status
3a) git cl dcommit   # checks the tree status before committing

To force a commit on a closed tree (for example, to unbreak the tree),
use the -f (force) flag to dcommit.

This info has been added to the using-git page on dev.chromium.org as well.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~--~~~~--~~--~--~---



[chromium-dev] Re: Proxy Service

2008-10-28 Thread Darin Fisher
Can we just make all platforms support globs and masks?
-Darin


On Tue, Oct 28, 2008 at 6:26 AM, Avi Drissman <[EMAIL PROTECTED]> wrote:

> I was actually reconsidering this on the way to work today. I'm trying to
> find some documentation for the Mac list, and I think it does handle
> asterisks too. I now don't think doing a split is worth the bother.
>
> (Back to code...)
>
> Avi
>
>
> On Mon, Oct 27, 2008 at 6:41 PM, Darin Fisher <[EMAIL PROTECTED]> wrote:
>
>> On Mon, Oct 27, 2008 at 2:12 PM, Avi Drissman <[EMAIL PROTECTED]> wrote:
>>
>>> WPAD just means use http://wpad/wpad.dat as the PAC URL.  This is
 supported by Firefox on all platforms, and it is easy to support in Chrome
 ;-)

>>>
>>> Right, but the question is where the switch is. Firefox uses its own UI
>>> (and IIRC doesn't use system proxy settings) so there's a place to turn that
>>> on/off. There's a switch in the headers:
>>> kSCPropNetProxiesProxyAutoDiscoveryEnable, but I don't know where that lives
>>> in the UI.
>>>
>>>
 Interesting.  Mozilla supports that syntax as well.  Is the expectation
 that hostnames will be resolved prior to consulting that list?

>>>
>>> I'd hope so. Otherwise... eew.
>>>
>>> BTW, I'm splitting the "seeing if the site is on the list" per-platform.
>>> Each platform seems to have different rules (the Mac has CIDR, Windows has
>>> "", etc).
>>>
>>
>>
>> It doesn't sound like a platform difference really.  I think it would be
>> better to just support that masking syntax in addition to globs.  Or, maybe
>> we can have an #ifdef that controls whether we support that or globs.  We
>> could also just have two separate .cc files, and only compile one or the
>> other.  Or, was there some OS API that would do the parsing and comparing
>> for you?
>>
>> -Darin
>>
>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~--~~~~--~~--~--~---