5 ms·

This is really interesting, because whilst Qt Webkit was a fantastic effort it had some quirks. Last project I was working on used Qt Webkit to provide a basic

This is really interesting, because whilst Qt Webkit was a fantastic effort it had some quirks. Last project I was working on used Qt Webkit to provide a basic browser, so there was lots of fun with flash player integration, Javascript going awry and so on, if they're relying on Chromium to act as the core it should remove a lot of those headaches for developers and allow them to build on top of it much easier. Definitely a big change, quite exciting though.

jdboyd 13y ago
Since Chromium doesn't support flash (that is one of the closed source bits added to Chrome), I suspect that while QTWebKit had fun with flash integration, Qt WebEngine will probably make Flash integration impossible. The worst part (at least for where I work) of using Flash in QtWebView was the non-availability of a license to just include the flash .dll in our application distribution.
- nicholassmith 13y ago
  I thought whilst Chromium didn't get the closed source bits, they were getting access through PPAPI, as everything else was on NPAPI and Adobe & Google decided to shift off it? I could be wrong though it's been a while since I last looked into it, and there was a lot of he-said-she-said on email lists about it at that point.
- teho 13y ago
  >Since Chromium doesn't support flash (that is one of the closed source bits added to Chrome) The Chrome PPAPI Flash Player works perfectly on Chromium and the binary can be shipped separately.
  - azakai 13y ago
    In principle, but does Adobe ship the Flash PPAPI binary separately?
    - gcr 13y ago
      How do other WebKit-based browsers like Luakit get flash to work? I thought they were always using the NS Plugin API for Flash. Is that being deprecated; is PPAPI a replacement?
      - gsnedders 13y ago
        Adobe no longer support (except for security updates) the NPAPI (not NSAPI) plugin on Linux, which also has a habit of crashing a lot and randomly hanging… If you want Flash to work under Linux, one practically has to use the PPAPI plugin. Note nobody except Chrome (and those based on the Chromium Content API) has any plan to support PPAPI, so in that sense NPAPI is alive and strong.

jdboyd 13y ago

Since Chromium doesn't support flash (that is one of the closed source bits added to Chrome), I suspect that while QTWebKit had fun with flash integration, Qt WebEngine will probably make Flash integration impossible. The worst part (at least for where I work) of using Flash in QtWebView was the non-availability of a license to just include the flash .dll in our application distribution.

nicholassmith 13y ago
I thought whilst Chromium didn't get the closed source bits, they were getting access through PPAPI, as everything else was on NPAPI and Adobe & Google decided to shift off it? I could be wrong though it's been a while since I last looked into it, and there was a lot of he-said-she-said on email lists about it at that point.
teho 13y ago
>Since Chromium doesn't support flash (that is one of the closed source bits added to Chrome) The Chrome PPAPI Flash Player works perfectly on Chromium and the binary can be shipped separately.
- azakai 13y ago
  In principle, but does Adobe ship the Flash PPAPI binary separately?
  - gcr 13y ago
    How do other WebKit-based browsers like Luakit get flash to work? I thought they were always using the NS Plugin API for Flash. Is that being deprecated; is PPAPI a replacement?
    - gsnedders 13y ago
      Adobe no longer support (except for security updates) the NPAPI (not NSAPI) plugin on Linux, which also has a habit of crashing a lot and randomly hanging… If you want Flash to work under Linux, one practically has to use the PPAPI plugin. Note nobody except Chrome (and those based on the Chromium Content API) has any plan to support PPAPI, so in that sense NPAPI is alive and strong.