Bug 679 – QWebPage miss extension function

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 679 - QWebPage miss extension function

Summary:

QWebPage miss extension function

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	1.0.0 beta4
Platform:	All All

Importance:	P2 normal
Assigned To:	Hugo Parente Lima

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-02-10 08:35 EET by flyaflya
Modified:	2011-03-04 15:10 EET (History)
CC List:	8 users (show)

See Also:

Attachments
QWebPage.supportsExtension can be call, but QWebPage.extension never be called (1.60 KB, text/plain) 2011-02-10 08:35 EET, flyaflya	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description flyaflya 2011-02-10 08:35:23 EET

Created attachment 263 [details]
QWebPage.supportsExtension can be call, but QWebPage.extension never be called

I need use QWebPage.supportsExtension and
QWebPage.extension(http://doc.qt.nokia.com/4.7-snapshot/qwebpage.html#extension)
 to deal with the error page,but I find extension can't be call and the
document( http://www.pyside.org/docs/pyside/PySide/QtWebKit/QWebPage.html) has
no this function. So I think it maybe be missed.

Comment 1 Hugo Parente Lima 2011-02-10 10:52:56 EET

I checked and saw that all inner classes of QWebPage are missing, so all
methods that use those classes were not generated, prioritizing as P2.

Comment 2 Hugo Parente Lima 2011-02-11 17:24:12 EET

Fixed in commit:

pyside/7b4d24f09459d3005314e366f13d3473c4236019

Comment 3 Hugo Parente Lima 2011-02-17 19:18:24 EET

Released in 1.0.0~rc1

Comment 4 flyaflya 2011-02-19 05:36:34 EET

(In reply to comment #3)
> Released in 1.0.0~rc1

I've tried rc1 on windows, the function "extension" can be call back when
getting a error page,but I found the function's parameters' types are not
right. For:

def extension(self, extens, info, errorPage):

info should be ErrorPageExtensionOption
[http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/qwebpage-errorpageextensionoption.html],
so info.errorString can get error message.

errorPage should be ErrorPageExtensionReturn
[http://doc.qt.nokia.com/4.7-snapshot/qwebpage-errorpageextensionreturn.html].

But they are ExtensionOption and ExtensionReturn now, and they have nothing
useful.

Comment 5 Hugo Parente Lima 2011-02-21 16:06:06 EET

This is another bug, the function and the missing classes are there, but not
working properly(In reply to comment #4)
> (In reply to comment #3)
> > Released in 1.0.0~rc1
> 
> I've tried rc1 on windows, the function "extension" can be call back when
> getting a error page,but I found the function's parameters' types are not
> right. For:
> 
> def extension(self, extens, info, errorPage):
> 
> info should be ErrorPageExtensionOption
> [http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/qwebpage-errorpageextensionoption.html],
> so info.errorString can get error message.
> 
> errorPage should be ErrorPageExtensionReturn
> [http://doc.qt.nokia.com/4.7-snapshot/qwebpage-errorpageextensionreturn.html].
> 
> But they are ExtensionOption and ExtensionReturn now, and they have nothing
> useful.

Now I see, the C++ API is based on a forced cast, so the types are useless.
This is a different bug (bug 694).

P.S.: Re-closign the bug.

Comment 6 Hugo Parente Lima 2011-03-04 15:10:43 EET

Closing bug due to 1.0.0 release.