jam
2013/06/27 21:22:51
can't do this.. chrome can't include anything inte
can't do this.. chrome can't include anything internal from content even
temporarily. please see the content api wiki
http://www.chromium.org/developers/content-module/content-api
since we don't have implementation inheritance in the content api, how we
usually solve this is moving to containment instead
scherkus (not reviewing)
2013/06/27 21:29:31
Can you give an example?
Do you mean wrapping a W
On 2013/06/27 21:22:51, jam wrote:
> can't do this.. chrome can't include anything internal from content even
> temporarily. please see the content api wiki
> http://www.chromium.org/developers/content-module/content-api
>
> since we don't have implementation inheritance in the content api, how we
> usually solve this is moving to containment instead
Can you give an example?
Do you mean wrapping a WebKit::WebMediaPlayer object + reimplementing the
interface + forwarding all the methods?
As an aside ... do you know why this scrutiny wasn't applied to anything under
src/webkit/ during content-ification of chrome? Was it out of scope?
jam
2013/06/28 00:31:58
what i mean is that the prerendering code doesn't
On 2013/06/27 21:29:31, scherkus wrote:
> On 2013/06/27 21:22:51, jam wrote:
> > can't do this.. chrome can't include anything internal from content even
> > temporarily. please see the content api wiki
> > http://www.chromium.org/developers/content-module/content-api
> >
> > since we don't have implementation inheritance in the content api, how we
> > usually solve this is moving to containment instead
>
> Can you give an example?
>
> Do you mean wrapping a WebKit::WebMediaPlayer object + reimplementing the
> interface + forwarding all the methods?
what i mean is that the prerendering code doesn't implement the interface, it
inherits from the implementation. we don't allow implementation inheritance in
the content api, since that would mean exposing internal implementation details
of content.
it's best to study that code to see exactly what prerendering needs to do. there
may be simpler ways of achieving this.
>
> As an aside ... do you know why this scrutiny wasn't applied to anything under
> src/webkit/ during content-ification of chrome? Was it out of scope?
the chrome/content split was done for code in src/chrome. we didn't touch other
top level directories like wekbit, net etc.
Issue 18123002: Migrate webkit/renderer/media/ to content/renderer/media/.
(Closed)
Created 7 years, 5 months ago by scherkus (not reviewing)
Modified 7 years, 5 months ago
Reviewers: ddorwin, jam, ycheo (away)
Base URL: svn://svn.chromium.org/chrome/trunk/src
Comments: 38