qt/qtwebengine.git - Qt WebEngine

	Commit message (Collapse)	Author	Age	Files	Lines
*	Re-enable some qwebenginesetting features in browser example	Allan Sandfeld Jensen	2014-08-19	1	-1/+1
\| \| \| \| \| \| \| \|	We now have the QWebEngineSettings class and can re-enable the features that were previously disabled in the browser that depended on it. Change-Id: I525dd1a4b5c380ad4c6060f276440e069f633897 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
*	Add api to get the favicon URL	Allan Sandfeld Jensen	2014-07-30	1	-5/+1
\| \| \| \| \| \| \| \| \| \| \|	Adds one of the missing pieces of the QWebFrame and QWebView APIs. Unlike the QtWebKit version this only fetches the favicon URL, and not the icon. This is because we do not want to implement an icon database, and that the icon would be loaded asynchronous anyway, bringing no guarantee to be a valid icon/image yet. Change-Id: I227311ae3676044da850e687b82bee752b5079c8 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
*	Fix up tabbed browser code.	Michael Brüning	2014-05-19	1	-4/+4
\| \| \| \| \|	Change-Id: Ia1a92a7eb9b3568e8cb7ccf6c7056abba647fd8d Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
*	Add linkHovered support for Widgets API	Szabolcs David	2014-05-15	1	-6/+2
\| \| \| \| \| \| \| \|	Drop hovered title and link text parameters, as we did in the Quick API. Change-Id: Ia1a38e0d728afbcbb6858a890486772da74aa813 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
*	Cleanup the QtWebEngineWidgets public headers and API	Jocelyn Turcotte	2014-04-15	1	-0/+18
\| \| \| \| \| \| \| \| \| \| \| \| \|	Headers were left intact to leave a trace of the evolution compared to the QtWebKit API and to make it easier to work until we had a basic subset of the API implemented. With the upcoming release, this patch removes this convenience in the aim of starting polishing the headers and the documentation for the upcoming release. Change-Id: Iae436b4ec041d771a7002575e122835802bc9f3e Reviewed-by: Michael Bruning <michael.bruning@digia.com>
*	Rename example directories to match the source install destination	Jocelyn Turcotte	2014-03-19	1	-0/+839
	To match other modules example directory structures we should deploy our examples in a directory matching the module name, webengine and webenginewidgets in our case. qmake uses the relative directory of each example up to the upper "examples" directory to decide where they will be deployed when running the sources install target. Change-Id: I59ce7ff8a30f98fad20064c7eecf72b784f1d275 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>