{"push_id":705689640,"size":1,"distinct_size":1,"ref":"refs/heads/for_upstream/jb30162_external_gl_context","head":"e214344b0415789a22e46313542c2aa2ef5fe0ca","before":"8bb1061a9e994729807ae739a4710226219a0d28","commits":[{"sha":"e214344b0415789a22e46313542c2aa2ef5fe0ca","author":{"email":"ff7039ee4dde76aca52b376af3312d4fbb92b3e8@jollamobile.com","name":"Piotr Tworek"},"message":"[embedlite] Add support for creating external GL context early. JB#30162\n\nIn sailfish browser we're interested in creating external window\ncompositing surface as early as possible. To avoid seeing any rendering\nartifacts / content from a previously rendered web page we want to reset\nthe state of the surface to a know state. Unfortunately gecko creates\nit's compositor context after the page being loaded requests it's first\nframe to be painted. In majority of cases this is to late for us.\n\nThis patch introduces an additional gecko pref which asks the embedder\nto create it's GL context as soon as top level PuppetWidget is created\nfor the view. The initial request is made from the compositor thread\nsince the GLContext object created by the application will be used from\nthis thread. The PuppetWidget does not do any caching of the requested\ncontext. It's expected that this part will be handled by the application\nitself (already the case for sailfish-browser).","distinct":true,"url":"https://api.github.com/repos/tworaz/gecko-dev/commits/e214344b0415789a22e46313542c2aa2ef5fe0ca"}]}