Also, unless you do something like this, it ends up being difficult for
developers to dogfood the product, or if they do try to dogfood the product,
then they are strongly inscentivized not to run the ui_tests. Neither
option is good.
-Darin
On Wed, Apr 8, 2009 at 11:21 AM, Darin Fisher
Note that a NOTIMPLEMENTED() prints when the code runs that tries to
abort when Chromium is already running.
One thing that I think has helped us on Linux is reducing the
NOTIMPLEMENTED prints to the bare minimum -- for stuff that we know is
broken (like the star button on the toolbar) having it
It helps to bucket Issues into milestones. So far we have had numbered
milestones like 2 and 2.1. However, I think it makes sense to have a
MStone:Mac and an MStone:Linux as well. I am moving Mac and Linux issues
into these. Basically if an issue it in these buckets we would expect it to
be
I can see how that's happening in pref_service_uitest.cc and
memory_test.cc, but AFAICT I don't see how it's being done generally
for ui_tests test cases. Perhaps it's that --user-data-dir should be
passed to ui_tests itself, which means if you run ui_tests without
that flag, it will still use
Another thing you should be able to do with an extension.
Note that our current proposals for a bookmark API don't have an index
property (within the parent). We need to add that.
- a
-- Forwarded message --
From: mertoman merto...@gmail.com
Date: Tue, Apr 7, 2009 at 8:03 AM
Hi all,
I fleshed out a few more APIs. I've put them in separate documents since the
API pattern doc was getting a bit long. Below are some notes, feedback
appreciated.
In particular, I'd love feedback from Scott on history and from Paul on
downloads.
-Nick
For downloads, do we provide a way for people to download a file
without showing a UI? It'd be interesting to do that and give people
the ability to register for callbacks. That might be useful for custom
download manager extensions... what I mean by that are extensions that
fetch every link on
