- Work in progress: Implement form completion / password save
- Konqueror integration;
- User defined custom stylesheets are working but the accessibility stylesheet is not.
- Extensions like e.g. Akregator newsfeed and WebArchiver. Some like the uachangerplugin are already working fine.
- Need a way to expose functions to JS that is more powerful than the current support for exposing the slots on a QObject. We need to be able to add functions directly to the window object so that we can expose methods directly without a containing object.
- We also need a way to be able to expose methods that are defined at run time. For example if we wanted to implement something like the flash-js bridge where we do not know at compile time which methods should be available we cannot implement this using the current API.
- Not sure if we can workaround this one, though something might be possible if you created a metaobject on the fly.
- Need a way to render block level elements directly to a QPaintDevice, specifically divs. These are divs that can be dragged out of a website onto the the desktop and will remain updated. One possibility is that the elements returned by a QWebElement search could have a paint( QPaintDevice * ) method.
- Workaround: Maybe find the bounding box of the element and paint that? Horrible hack and will not handle elements that have an alpha channel very well.
- Need a way to integrate QtWebKit into KWallet. There are problems on some pages where JS clears form contents late in the page load sequence, after eg KWallet may have present the form contents.
- KDE features to form widgets etc. It is not known how to integrate KDE features such as text completion with the versions of these features implemented in JS in the web page. Currently since the AJAX mostly does not work in KHTML, the KDE versions are used.
- Configuration management using kcontrol. QWebSetting is used to get settings into Webkit
- Adblock - relies on DOM hacking. Could be implemented using the QWebElement API.
- How do we integrate java? There are 2 ways Java is integrated, via the <embed> element or as applets via the NPAPI. The problem with the NPAPI system is that existing Java plugins also rely on XPCOM. <applet> is mapped atm by QWebKit to <embed>.
- All of the QWebKit api is in the webkit repo, it is NOT in the qt gitorious. We should work at the webkit repo and submit patches there like other contributors, not work in a 'fork' git branch.
- on #webkit we can get the trolls to help review patches.
- Not loading the right thing when linking to other data types eg. text files, or spreadsheets. QWebPluginFactory should be usable to load KParts. There were some questions whether this would be able to react to dynamic changes to the set of available plugins - need way to tell the Factory to reload its plugin list.
- How to suppress right click menu.
- How do we get information about which resources comprise a particular page to implement something like the web archive plugin. The information is present in the web inspector but we have no access to it.
- State saving/loading for eg 'Undo Close Tab'
- Font size (screen dimensions) need to be communicated correctly to WebKit. Gof is working on a platform plugin to get font sizes in.
- Plugins. WebArchiver needs access to the source so it can store it and the resources it references (images,css) and edit the dom so the references point to the local copies. This may be possible with QWebInspector. Could also watch things coming through QNetworkAccessManager, but this would break when there are interleaved page requests. Perhaps KIO cache should be used to get and save these resources without reloading 2Mb web pages.
- Improving plugin support in Konqueror is desirable but orthogonal to fixing the web experience
This page was last modified on 15 November 2009, at 14:56. This page has been accessed 5,129 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.