Release notes for M9.

Release notes for M9.

TEST=none
BUG=none


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=68895

[PhistucK, 2010-12-10 18:15:01]

http://codereview.chromium.org/5748001/diff/5001/chrome/common/extensions/doc...
File chrome/common/extensions/docs/static/whats_new.html (right):

http://codereview.chromium.org/5748001/diff/5001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/whats_new.html:42: and into a new window.
</li>
If I am not mistaking, the other purpose of this change was to move a popup to
be a tab. If this is the case, this also should be mentioned (you could have
moved tabs to new windows before, I think, just by using two API calls instead
of one).

[Aaron Boodman, 2010-12-10 18:24:52]

LGTM

I just remembered, the homepage_url is also new:

http://code.google.com/chrome/extensions/manifest.html#homepage_url

We should make it a practice when making API changes to update this
page too I guess, so we don't forget. Then you can just copy edit it.

- a

On Fri, Dec 10, 2010 at 10:15 AM,  <phistuck@gmail.com> wrote:
>
>
http://codereview.chromium.org/5748001/diff/5001/chrome/common/extensions/doc...
> File chrome/common/extensions/docs/static/whats_new.html (right):
>
>
http://codereview.chromium.org/5748001/diff/5001/chrome/common/extensions/doc...
> chrome/common/extensions/docs/static/whats_new.html:42: and into a new
> window. </li>
> If I am not mistaking, the other purpose of this change was to move a
> popup to be a tab. If this is the case, this also should be mentioned
> (you could have moved tabs to new windows before, I think, just by using
> two API calls instead of one).
>
> http://codereview.chromium.org/5748001/
>

[kathyw, 2010-12-10 18:31:03]

> I just remembered, the homepage_url is also new:
>
> http://code.google.com/chrome/extensions/manifest.html#homepage_url

That reminds me... If you host in the web store, is the store's URL
for the app/extension the default value?

> We should make it a practice when making API changes to update this
> page too I guess, so we don't forget. Then you can just copy edit it.

That makes sense. Do we have a page somewhere that lists what to do
when you add an API? Or maybe this should just be a comment in the
source code.

Also, should I mention something about this:

>> If I am not mistaking, the other purpose of this change was to move a
>> popup to be a tab. If this is the case, this also should be mentioned
>> (you could have moved tabs to new windows before, I think, just by using
>> two API calls instead of one).

-k-


On Fri, Dec 10, 2010 at 10:24 AM, Aaron Boodman <aa@chromium.org> wrote:
> LGTM
>
> I just remembered, the homepage_url is also new:
>
> http://code.google.com/chrome/extensions/manifest.html#homepage_url
>
> We should make it a practice when making API changes to update this
> page too I guess, so we don't forget. Then you can just copy edit it.
>
> - a
>
> On Fri, Dec 10, 2010 at 10:15 AM,  <phistuck@gmail.com> wrote:
>>
>>
http://codereview.chromium.org/5748001/diff/5001/chrome/common/extensions/doc...
>> File chrome/common/extensions/docs/static/whats_new.html (right):
>>
>>
http://codereview.chromium.org/5748001/diff/5001/chrome/common/extensions/doc...
>> chrome/common/extensions/docs/static/whats_new.html:42: and into a new
>> window. </li>
>> If I am not mistaking, the other purpose of this change was to move a
>> popup to be a tab. If this is the case, this also should be mentioned
>> (you could have moved tabs to new windows before, I think, just by using
>> two API calls instead of one).
>>
>> http://codereview.chromium.org/5748001/
>>
>

[Aaron Boodman, 2010-12-10 19:00:09]

On 2010/12/10 18:31:03, kathyw wrote:
> > I just remembered, the homepage_url is also new:
> >
> > http://code.google.com/chrome/extensions/manifest.html#homepage_url
> 
> That reminds me... If you host in the web store, is the store's URL
> for the app/extension the default value?

Yes it is.

> > We should make it a practice when making API changes to update this
> > page too I guess, so we don't forget. Then you can just copy edit it.
> 
> That makes sense. Do we have a page somewhere that lists what to do
> when you add an API? Or maybe this should just be a comment in the
> source code.

Yeah there should be.

> Also, should I mention something about this:
> 
> >> If I am not mistaking, the other purpose of this change was to move a
> >> popup to be a tab. If this is the case, this also should be mentioned
> >> (you could have moved tabs to new windows before, I think, just by using
> >> two API calls instead of one).

It's true that was the motivation. Maybe you could just add a "for example, you
could use this to ..." in the description of that method?

- a

[kathyw, 2010-12-10 22:17:16]

Aaron, could you take another look?

-k-

[Aaron Boodman, 2010-12-10 22:25:19]

lgtm

[PhistucK, 2010-12-11 07:27:41]

You wrote "tab or panel", why not "tab\popup\panel"?...

Thank you. :)