Version: (using KDE 3.5.5) Installed from: Debian stable Packages OS: Linux Hi, There is a first draft of the HTML5 available[1]. For the moment, the only browser I know which support this draft is firefox 3 (a special build). But looking to the possibility that we will have with this release, I found it will be really important to support it in a futur release of KHTML. I don't know of this already planed, but I guess it will be a very "wanted" feature. [1] http://www.w3.org/2008/02/html5-pressrelease
Hello: Any news about html5 support on konqueror? Thanks.
For the audio/video part of HTML 5, see #145380
As much as I agree that we want HTML5 support I don't think this bug is very useful. HTML5 consists of so many different parts (forms, canvas, DOM, video, ...) that tracking the whole in one bug doesn't look right. This would probably stay open for years as only parts will be implemented at a time and there would be something left for quite a while. I think adding whishlist or bug entries for smaller parts would be much more useful.
Rolf is right, but meanwhile I happen to test this: http://www.nevermindthebullets.com/strip.html#1-1 which looks that already implements some of the HTML5 parts: * Font face loading * SVG background * Header & Section layout * JavaScript acceleration * CSS3 Multi-background * Editable content <Taken from http://www.nevermindthebullets.com/> In summary, someone with enough knowlegde should state which of the HTML5 parts are still missing. Regards,
(In reply to comment #3) > As much as I agree that we want HTML5 support I don't think this bug is very > useful. HTML5 consists of so many different parts (forms, canvas, DOM, video, > ...) that tracking the whole in one bug doesn't look right. This would probably > stay open for years as only parts will be implemented at a time and there would > be something left for quite a while. I think adding whishlist or bug entries > for smaller parts would be much more useful. IMHO the correct answer is to keep this bug report open and add all bug reports on smaller parts of HTML5 as *dependencies* of this bug. This way you can have your individual bug reports on each missing feature of HTML5 plus you know when to close this bug report (when all dependencies are resolved).
I want to add bug 264201 as dependency. How to?
Hello, as filed, this bug report is not useful. The only way to file useful bug reports with regards to HTML5 is to identify in unique bug reports and with a reduced, minimized testcase which single elements and which single attributes are not supported in Konqueror. There is a HTML5 test suite which is *_still in development_* (just like HTML5 spec itself is still in development): the test suite is not in its stable and final version. So, it's possible that some tests in that test suite would be invalid. E.g. http://w3c-test.org/html/tests/approved/xhtml5/img_border_percent.xhtml http://w3c-test.org/html/tests/approved/xhtml5/object_border_perc.xhtml http://w3c-test.org/html/tests/approved/xhtml5/object_border_pixel.xhtml are 3 invalid testcases. Nevertheless, we can stil find good testcases from the test suite which can identify the elements and attributes which are not supported. HTML5 test suite (Draft) http://w3c-test.org/html/tests/harness/harness.htm Please keep in mind that " Unfortunately due to the large number of bug reports received, and the large amount of time that it takes developers to identify issues, reports which do not include a testcase or are not described in reproduceable steps will get a low priority of fixing. (...) 5. The important part is: the page should be as short as possible to be able to still reproduce the bug. The shorter it is, the sooner it will get fixed! " Investigating Konqueror Bugs http://www.konqueror.org/investigatebug/ Gérard Talbot
Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann