Expose GetLastCommitedOrigin() on WebContents and use it in about:blank

Expose GetLastCommitedOrigin() on WebContents and use it in about:blank
site identity.

Expose GetLastCommittedOrigin() on content::WebContents and display it in
about:blank page's site identity when it is opened by another frame.

Screenshot: https://code.google.com/p/chromium/issues/detail?id=469889#c48

BUG=469889, 498580, 466422
R=meacer@chromium.org,felt@chromium.org,nasko@chromium.org,creis@chromium.org

TBR=cpu@chromium.org

TEST=Start Chrome.
Navigate to google.com (or any website).
Run 'window.open()' from the page.
Bring up the Chrome Security UI bubble.
(Its disabled right now, you need to enable it locally)
Site identity section should show origin as opener's host.

[upendrag.gowda, 2015-11-19 03:53:29]

Description was changed from

==========
Expose GetLastCommitedOrigin() on WebContents and use it in about:blank
site identity.

Expose GetLastCommittedOrigin() on content::WebContents and display it in
about:blank page's site identity when it is opened by another frame.

Screenshot:

BUG=469889,498580,466422
R=meacer@chromium.org,felt@chromium.org,nasko@chromium.org,creis@chromium.org,

TEST=Start Chrome.
Navigate to google.com (or any website).
Run 'window.open()' from the page.
Bring up the Chrome Security UI bubble.
(Its disabled right now, you need to enable it locally)
Site identity section should show origin as opener's host.
==========

to

==========
Expose GetLastCommitedOrigin() on WebContents and use it in about:blank
site identity.

Expose GetLastCommittedOrigin() on content::WebContents and display it in
about:blank page's site identity when it is opened by another frame.

Screenshot: https://code.google.com/p/chromium/issues/detail?id=469889#c48

BUG=469889,498580,466422
R=meacer@chromium.org,felt@chromium.org,nasko@chromium.org,creis@chromium.org

TBR=cpu@chromium.org

TEST=Start Chrome.
Navigate to google.com (or any website).
Run 'window.open()' from the page.
Bring up the Chrome Security UI bubble.
(Its disabled right now, you need to enable it locally)
Site identity section should show origin as opener's host.
==========

[felt, 2015-11-19 05:32:38]

felt@chromium.org changed reviewers:
+ lgarron@chromium.org

[felt, 2015-11-19 05:32:39]

upendrag.gowda: I hate to be the bearer of bad news, but the connection panel of
the OIB is due to be deleted with Chrome 49. :( We replaced it with the new
Security Panel, which was just launched with Chrome 48.

I think it would still be nice to incorporate the origin source information into
the OIB. It just can't go into the connection tab, because that is going to be
deleted.

lgarron, do you have any thoughts on where else the origin source info could go
in the OIB?

[lgarron, 2016-03-17 00:06:19]

On 2015/11/19 at 05:32:39, felt wrote:
> upendrag.gowda: I hate to be the bearer of bad news, but the connection panel
of the OIB is due to be deleted with Chrome 49. :( We replaced it with the new
Security Panel, which was just launched with Chrome 48.
> 
> I think it would still be nice to incorporate the origin source information
into the OIB. It just can't go into the connection tab, because that is going to
be deleted.
> 
> lgarron, do you have any thoughts on where else the origin source info could
go in the OIB?

So, the connection tab is finally gone now.

However, the top of Page Info currently shows:

    about:blank
    Your connection to this site is not private.
    [Details]

As long as we still allow navigations to pages that show up with a URL of
about:blank, I think it would be appropriate to update those strings instead.
Perhaps:

    about:blank (google.com)
    This page is opened and controlled by <ph
name="DOMAIN">$1<ex>www.google.com</ex></ph>.

[meacer, 2016-03-17 00:08:26]

On 2016/03/17 00:06:19, lgarron wrote:
> On 2015/11/19 at 05:32:39, felt wrote:
> > upendrag.gowda: I hate to be the bearer of bad news, but the connection
panel
> of the OIB is due to be deleted with Chrome 49. :( We replaced it with the new
> Security Panel, which was just launched with Chrome 48.
> > 
> > I think it would still be nice to incorporate the origin source information
> into the OIB. It just can't go into the connection tab, because that is going
to
> be deleted.
> > 
> > lgarron, do you have any thoughts on where else the origin source info could
> go in the OIB?
> 
> So, the connection tab is finally gone now.
> 
> However, the top of Page Info currently shows:
> 
>     about:blank
>     Your connection to this site is not private.
>     [Details]
> 
> As long as we still allow navigations to pages that show up with a URL of
> about:blank, I think it would be appropriate to update those strings instead.
> Perhaps:
> 
>     about:blank (http://google.com)
>     This page is opened and controlled by <ph
> name="DOMAIN">$1<ex>www.google.com</ex></ph>.

That sounds good to me.
@upendrag.gowda: Are you still interested in landing this patch?

[upendrag.gowda, 2016-03-17 00:24:48]

On 2016/03/17 00:08:26, Mustafa Emre Acer wrote:
> On 2016/03/17 00:06:19, lgarron wrote:
> > On 2015/11/19 at 05:32:39, felt wrote:
> > > upendrag.gowda: I hate to be the bearer of bad news, but the connection
> panel
> > of the OIB is due to be deleted with Chrome 49. :( We replaced it with the
new
> > Security Panel, which was just launched with Chrome 48.
> > > 
> > > I think it would still be nice to incorporate the origin source
information
> > into the OIB. It just can't go into the connection tab, because that is
going
> to
> > be deleted.
> > > 
> > > lgarron, do you have any thoughts on where else the origin source info
could
> > go in the OIB?
> > 
> > So, the connection tab is finally gone now.
> > 
> > However, the top of Page Info currently shows:
> > 
> >     about:blank
> >     Your connection to this site is not private.
> >     [Details]
> > 
> > As long as we still allow navigations to pages that show up with a URL of
> > about:blank, I think it would be appropriate to update those strings
instead.
> > Perhaps:
> > 
> >     about:blank (http://google.com)
> >     This page is opened and controlled by <ph
> > name="DOMAIN">$1<ex>www.google.com</ex></ph>.
> 
> That sounds good to me.
> @upendrag.gowda: Are you still interested in landing this patch?

Yes, I am interested. But I am not sure if I can take this up before March 30 (2
weeks from now), since I have  project deadlines and midterms coming up. Let me
know if that is OK for you.

[meacer, 2016-03-17 00:46:01]

On 2016/03/17 00:24:48, upendrag.gowda wrote:
> On 2016/03/17 00:08:26, Mustafa Emre Acer wrote:
> > On 2016/03/17 00:06:19, lgarron wrote:
> > > On 2015/11/19 at 05:32:39, felt wrote:
> > > > upendrag.gowda: I hate to be the bearer of bad news, but the connection
> > panel
> > > of the OIB is due to be deleted with Chrome 49. :( We replaced it with the
> new
> > > Security Panel, which was just launched with Chrome 48.
> > > > 
> > > > I think it would still be nice to incorporate the origin source
> information
> > > into the OIB. It just can't go into the connection tab, because that is
> going
> > to
> > > be deleted.
> > > > 
> > > > lgarron, do you have any thoughts on where else the origin source info
> could
> > > go in the OIB?
> > > 
> > > So, the connection tab is finally gone now.
> > > 
> > > However, the top of Page Info currently shows:
> > > 
> > >     about:blank
> > >     Your connection to this site is not private.
> > >     [Details]
> > > 
> > > As long as we still allow navigations to pages that show up with a URL of
> > > about:blank, I think it would be appropriate to update those strings
> instead.
> > > Perhaps:
> > > 
> > >     about:blank (http://google.com)
> > >     This page is opened and controlled by <ph
> > > name="DOMAIN">$1<ex>www.google.com</ex></ph>.
> > 
> > That sounds good to me.
> > @upendrag.gowda: Are you still interested in landing this patch?
> 
> Yes, I am interested. But I am not sure if I can take this up before March 30
(2
> weeks from now), since I have  project deadlines and midterms coming up. Let
me
> know if that is OK for you.

SG, given that the bug has been open for a long time, I think it can wait for
two more weeks.

[upendrag.gowda, 2016-04-07 17:40:59]

On 2016/03/17 00:46:01, Mustafa Emre Acer wrote:
> On 2016/03/17 00:24:48, upendrag.gowda wrote:
> > On 2016/03/17 00:08:26, Mustafa Emre Acer wrote:
> > > On 2016/03/17 00:06:19, lgarron wrote:
> > > > On 2015/11/19 at 05:32:39, felt wrote:
> > > > > upendrag.gowda: I hate to be the bearer of bad news, but the
connection
> > > panel
> > > > of the OIB is due to be deleted with Chrome 49. :( We replaced it with
the
> > new
> > > > Security Panel, which was just launched with Chrome 48.
> > > > > 
> > > > > I think it would still be nice to incorporate the origin source
> > information
> > > > into the OIB. It just can't go into the connection tab, because that is
> > going
> > > to
> > > > be deleted.
> > > > > 
> > > > > lgarron, do you have any thoughts on where else the origin source info
> > could
> > > > go in the OIB?
> > > > 
> > > > So, the connection tab is finally gone now.
> > > > 
> > > > However, the top of Page Info currently shows:
> > > > 
> > > >     about:blank
> > > >     Your connection to this site is not private.
> > > >     [Details]
> > > > 
> > > > As long as we still allow navigations to pages that show up with a URL
of
> > > > about:blank, I think it would be appropriate to update those strings
> > instead.
> > > > Perhaps:
> > > > 
> > > >     about:blank (http://google.com)
> > > >     This page is opened and controlled by <ph
> > > > name="DOMAIN">$1<ex>www.google.com</ex></ph>.
> > > 
> > > That sounds good to me.
> > > @upendrag.gowda: Are you still interested in landing this patch?
> > 
> > Yes, I am interested. But I am not sure if I can take this up before March
30
> (2
> > weeks from now), since I have  project deadlines and midterms coming up. Let
> me
> > know if that is OK for you.
> 
> SG, given that the bug has been open for a long time, I think it can wait for
> two more weeks.

Hi @meacer, I haven't been able to allocate time to work on this issue as agreed
before and it looks like the situation won't get any better for at least a month
as it's the end of semester. Please feel free to un-assign the task from me. 
Apologies for the delay caused

[meacer, 2016-04-07 17:42:59]

On 2016/04/07 17:40:59, upendrag.gowda wrote:
> On 2016/03/17 00:46:01, Mustafa Emre Acer wrote:
> > On 2016/03/17 00:24:48, upendrag.gowda wrote:
> > > On 2016/03/17 00:08:26, Mustafa Emre Acer wrote:
> > > > On 2016/03/17 00:06:19, lgarron wrote:
> > > > > On 2015/11/19 at 05:32:39, felt wrote:
> > > > > > upendrag.gowda: I hate to be the bearer of bad news, but the
> connection
> > > > panel
> > > > > of the OIB is due to be deleted with Chrome 49. :( We replaced it with
> the
> > > new
> > > > > Security Panel, which was just launched with Chrome 48.
> > > > > > 
> > > > > > I think it would still be nice to incorporate the origin source
> > > information
> > > > > into the OIB. It just can't go into the connection tab, because that
is
> > > going
> > > > to
> > > > > be deleted.
> > > > > > 
> > > > > > lgarron, do you have any thoughts on where else the origin source
info
> > > could
> > > > > go in the OIB?
> > > > > 
> > > > > So, the connection tab is finally gone now.
> > > > > 
> > > > > However, the top of Page Info currently shows:
> > > > > 
> > > > >     about:blank
> > > > >     Your connection to this site is not private.
> > > > >     [Details]
> > > > > 
> > > > > As long as we still allow navigations to pages that show up with a URL
> of
> > > > > about:blank, I think it would be appropriate to update those strings
> > > instead.
> > > > > Perhaps:
> > > > > 
> > > > >     about:blank (http://google.com)
> > > > >     This page is opened and controlled by <ph
> > > > > name="DOMAIN">$1<ex>www.google.com</ex></ph>.
> > > > 
> > > > That sounds good to me.
> > > > @upendrag.gowda: Are you still interested in landing this patch?
> > > 
> > > Yes, I am interested. But I am not sure if I can take this up before March
> 30
> > (2
> > > weeks from now), since I have  project deadlines and midterms coming up.
Let
> > me
> > > know if that is OK for you.
> > 
> > SG, given that the bug has been open for a long time, I think it can wait
for
> > two more weeks.
> 
> Hi @meacer, I haven't been able to allocate time to work on this issue as
agreed
> before and it looks like the situation won't get any better for at least a
month
> as it's the end of semester. Please feel free to un-assign the task from me. 
> Apologies for the delay caused

No worries, palmer@ picked this up in another CL already:
https://codereview.chromium.org/1814993002/
Thanks for the heads up!