Description
We're using moinmoin 1.8.0. I'm browsing the wiki using google chrome 1.0 (build 1.0.154.53). The option to edit wiki pages using gui mode is not available. Changing settings to explicitly make it available doesn't work. If I change my settings so that ONLY editing via gui should be made available, then only one Edit link shows up, and it still only allows text-mode editing. If I forcibly change the edit link to ...?action=edit&editor=gui, then the gui editor comes up, but any subsequent action (e.g., Preview) fails with ExpatError.
I don't know if you folks explicitly support chrome or not; if not, I guess this becomes a feature request instead.
Steps to reproduce
- Open non-immutable wiki page in google chrome 1.0.
- Attempt to edit page using gui mode.
Example
I can't really make a snapshot available since I can't prove the absence of something.
Component selection
I assume this has to do with the fckeditor you're using, but I wouldn't know for sure.
- common.js can_use_gui_editor needs to be adopted to chrome
Details
MoinMoin Version |
1.8.0 .. 1.8.4 |
OS and Version |
Windows XP SP3, also Ubuntu Linux 9.04 |
Python Version |
2.4.3 or 2.6 |
Server Setup |
RHEL 4 system, Ubuntu Linux 9.04 |
Server Details |
gcc 4.1.1 |
Language you are using the wiki in (set in the browser/UserPreferences) |
English |
Workaround
Don't use chrome.
Discussion
The User Agent that Chrome reports is "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.28 Safari/530.5".
expaterror.log and debug.html -- TimCera 2009-06-02 17:40:36
Moin can easily be changed to show the gui editor link for Safari and Google Chrome: fckeditor_webkit.diff
BUT: it looks like the html editor in webkit (i tested it with current google chrome) does not emit sanitized (x)html, so expat will complain about mismatching tags (e.g. <p> not followed by </p>). This is a problem in the moin html generation (that will be fixed by moin 2.0 after the dom code is merged, but we can't do much about that in moin < 2.0). So the only fix could be to make webkit sanitize the html, but I don't know whether it can do that. -- ThomasWaldmann 2009-09-06 14:07:10
Also, the current google chrome still has the editor sizing problem, as already noted above. -- ThomasWaldmann 2009-09-06 14:07:10
This is a general webkit problem. I tried it with a webkit based epiphany with the same problems. -- ThomasRenard 2011-08-03 09:16:11
Plan
- Priority:
- Assigned to:
Status: see http://moinmo.in/MoinMoinBugs/1.9.3GUIEditorInWebKit