On Wednesday, October 12, 2011 09:51:05 AM ext Kenneth Rohde Christiansen wrote: > I didn't mean that we will not support plugins at all, but we will not > invest in them as well. Plugins have serious issues and especially on > mobile devices with touch input etc. For this reason I guess we will > follow Apple, Microsoft etc and not support plugins on our > QTouchWebView.
Time will tell and things may change. But yeah, for the time being we have bigger challenges and our priority is getting trunk WebKit2 into great shape. Time is IMHO well spent right now on getting the process separation right (i.e. determine the right things to delegate to the ui process vs. using platform libraries in the web process) or getting the rendering design right so that implementing CSS shaders becomes a rather simple thing. Dawit, that's why plugins are of lower priority to us. Simon > On Wed, Oct 12, 2011 at 2:50 AM, Dawit A <[email protected]> wrote: > > On Tue, Oct 11, 2011 at 6:33 PM, Kenneth Rohde Christiansen > > <[email protected]> wrote: > >>> 7) QWidgets inside a page: do we have users for this? > >> > >> Plugins are on the way out :-) Let's let this feature rest in piece. > > > > If that is the case, then how is QtWebKit2 going to deal with the > > <embed> tag ? More specifically for embedding content type it does not > > support. For example, > > > > <embed type="application/pdf" > > src="http://ev.kde.org/reports/ev-quarterly-2011_Q2.pdf"; width="75%" > > height="400"/> > > > > > > -- > Kenneth Rohde Christiansen > Senior Engineer > Application and Service Frameworks, Nokia Danmark A/S > Phone +45 4093 0598 / E-mail kenneth.christiansen at gmail.com > > http://codeposts.blogspot.com ﹆﹆﹆ > > > > _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
