[Future Request] United Extensions API implementation.

[GoogleCodeExporter]

 Power of any browser in extensions. So it would be great to see in QtWeb implementation of most extensions APIs - 
Chrome Extensions API, Mozilla JetPack and WebKit2/Safari Extensions API(hope 
it will be WebKit2 extensions API).
These 3 extension types will be easy based on js+css+html and will fine work 
together if the same equivalent of API function will have 3 different meaning !
It will need to implement 3 API of extensions from these browsers. 
For example - 1 API call of Chrome Extension API has the same meaning in 
JetPack API and in WebKit2 Extensions API.

And I hope User Java Scripts will be easy to install like these extensions only 
by ".user.js" extension of file name.(like in Chrome now, by the way)

Please understand my F.R. correctly. Because of having 15 years browsing 
experience. And really tired of misunderstandings in the browser development. 
And QtWeb seems to me very powerful.

Original issue reported on code.google.com by dimac...@bk.ru on 11 Jun 2010 at 11:11

[GoogleCodeExporter]

Original comment by magis...@gmail.com on 28 May 2013 at 9:40

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by magis...@gmail.com on 28 May 2013 at 9:49