Bug 7932 – HTML editing API's not fully rendered and/or not working

• Component: JavaScriptCore
• Status: RESOLVED WORKSFORME

[Gustaaf Groenendaal (MysteryQuest)]

API's that help you build up your HTML in your browser without coding don't render completely and/or don't allow input. The reason is unclear for me at this time.

The Applications is using javascript for the input. The problem is that it is impossible to edit your content within the API. When switching to the HTML code and switch back to the layout view, you will notice that it tells "Even geduld graag..." (In English: "One moment please...") If the page is opened in WebKit without custom user-agent, no API is shown and only a plain HTML editor and ASCII editor are shown.

The API is used by some weblogs (as in the URL) and also Hotmail (untested).

The API in the URL is the API for Gecko based browsers. There is also an API that is build for MSIE, but that API is causing even much more problems in WebKit. I think we need to focus on the Gecko based API, because the API is more internet-standard compatible. A few changes would allow WebKit to work with this API.

A reduction for this API or a reduction from such an API in English would be greatly appreciated.

Tested with WebKit 417.9.2 and 420+. Maybe a hint for the hit list, because it is a hard one and is used more and more on today's internet web-pages.

[Mark Rowe (bdash)]

With WebKit r15138 I see three JavaScript errors which may affect this:

TypeError: Undefined value
http://www.mysteryquest.org/webkit/bugs/content_edit.html

Value undefined (result of expression obj.edit_object.stop) is not object.
http://www.mysteryquest.org/webkit/bugs/content_edit/MozScript.js

Error: NO_MODIFICATION_ALLOWED_ERR: DOM Exception 7
http://www.mysteryquest.org/webkit/bugs/content_edit/MozScript.js

That said, it works in Firefox so we should be able to get this working in WebKit.

Created attachment 10856 [details]
Demonstrates errors

Demonstrates the 2 errors that make the editor fail:
1) Window does not support stop(), as in window.stop(), which is "Used to stop a window from loading" (never heard of it before). That's the type-error
2) Safari doesn't allowing setting innerHTML og the HEAD-section, Firefox does. That's the NO_MODIFICATION error

The final bug is a bug in the page itself. This fails in Firefox too, and is simply because they reference an element that doesn't exist (not inside that element anyway (form closed too soon)).

Otherwise the editor seems to work

[Gavin Barraclough]

Safari does now support window.stop, and does support setting the innerHTML of the head.  Our behaviour on the test case now matches that of FireFox.  Works for me.