Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Konq conks ;-)
This is intended as an informational post rather than a bug report. I am going to file a bug report at KDE. BTW, this is Konq/KDE version 4.2.1. Entering the text box and typing one character causes the browser to crash. If I disable rich text I see that Konq has created a bunch of paragraph and break tags.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | wysiwyg-HEAD.konqueror.patch | 1.8 KB | sun |
Comments
Comment #1
sunCould you also test with Wysiwyg 2.x, please? Wysiwyg API implements a lot of JavaScript to load and attach editors - some parts of the logic are improved in 2.x.
Comment #2
eyecon-1 CreditAttribution: eyecon-1 commentedSure. I need to resync my local machine (which I crashed) to the server tonight.
Comment #3
TwoDI just installed Konqueror and tested it on two sites using 2.x. One where TinyMCE is the default editor, and one where I have FCKeditor.
TinyMCE works fine, until I try to type something and it crashes. FCKeditor doesn't load at all, don't know why as Konqueror doesn't show any errors. Switching to an input filter which has TinyMCE enabled doesn't work either, nothing happens.
A second textarea on one of my content types, which uses TinyMCE by default, works fine (if I don't type anything) until I switch to an input format which uses FCKeditor, then it breaks and is unrecoverable. The contents are replaced by "
<P><P><P><P><P><P> </P>".On a side-note: Admin Menu is completely messed up as well, the dropdown menues are very distorted and can't be read. I also noted that the original JavaScript code for splitting/joining the teaser, when Wysiwyg is not installed, looks for Konqueror and returns straight away without doing anything. Looks like this browser has some serious issues. :(
Comment #4
sunSo, since we cannot control which browser a user is using, shall we do the same as the teaser splitter for Konqueror?
Comment #5
eyecon-1 CreditAttribution: eyecon-1 commentedUpdated to 6.x-2.x-dev. No joy. I wouldn't worry about this since most people who have konq have other browsers anyway. KDE4 is still not fully ready for prime time.
Comment #6
eyecon-1 CreditAttribution: eyecon-1 commented"I just installed Konqueror and tested it on two sites using 2.x. One where TinyMCE is the default editor, and one where I have FCKeditor."
Perhaps I should have mentioned TinMCE=3.2.2
You can try to enter a comment on our site. Konq 4.2.1 will conk,
http://www.tips-q.com
The problem is with KDE not with WYSIWYG. I only mentioned it so that people can create a condition block on konqueror.
Comment #7
wewright CreditAttribution: wewright commentedActually I find that the exact same thing is happening with FireFox 3.0.8. I'm using WYSIWYG 6.x-1.1 and TinyMCE 3.2.2.3. Everything works fine in IE. I also see that when using the TinyMCE plugin (other Drupal project) that the core TinyMCE stuff seems to work fine. When using WYSIWYG 6.x-2.x-dev TinyMCE doesn't seem to show up at all.
Comment #8
sun@wewright: Whatever issue you have with Firefox (which I was not able to understand from your follow-up), it is completely off-topic for this issue, because we are specifically talking about Konqueror here.
Comment #9
wewright CreditAttribution: wewright commentedI did some more debugging and found that the tablet interface add-on I had for Firefox was what was actually crashing it. Must be something about the interaction with all the Javascript because it works fine in normal boxes but blows up when going into any fckEditor or TinyMCE in this. Disabling the Gesso plugin makes this work so I'd say it's definitely a different issue than the one you reported.
Comment #10
sun@wewright: Could you add this information to the #359936: FAQ, please?
Comment #11
sunCommitted attached patch as quick fix for now.
I'd be open to investigate support for Konqueror further in a separate issue.