Closed (fixed)
Project:
Wysiwyg
Version:
6.x-2.x-dev
Component:
Plugins
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Mar 2009 at 09:43 UTC
Updated:
10 Jun 2009 at 17:32 UTC
Jump to comment: Most recent file
Comments
Comment #1
sunWhat kind of "pagebreak" are you talking of?
Comment #2
fredklopper commentedDrupal break:
<!--break-->Comment #3
Arjean-1 commentedI can confirm this.
The page/teaser break button works perfect in Firefox, you can add it to a new/edit node and it will be stored.
As for IE7 it is already being filtered out at a preview.
When editing a post (having working teaser break) in Explorer 7 it will show the teaser break,
but every edit afterwards will make it disappear.
Comment #4
k3vin commentedsubscribing
Comment #5
sunComment #6
twodI did some testing in IE6 and it turns out that IE does not allow comments to be inserted the way we do it in the Break plugin.
The plugin uses
$('img.wysiwyg-break', $content).replaceWith('<!--break-->'), which in turn callsthis.after('<!--break-->'). Wrapping the comment in something, like<p><!--break--></p>seems to work though, but I'm not sure if it'll treat it as text or an actual comment though. I don't have access to my own computer at the moment but will test this again in a few hours.Comment #7
twodI've created a simple patch and tested it in IE7. It should also work in IE6 (and all other major browsers) since document.createComment() was introduced to the standards back then.
Comment #8
Arjean-1 commentedTested it in IE 7, Firefox 3 and Opera 9, seems to work fine. Well done.
Comment #9
sunComment #10
sunThanks for testing!
Committed attached patch to all 2.x branches.
We should always add remarks for compatibility issues like this.
Comment #11
fredklopper commentedWell done, thanks!!!
Comment #13
twodFor the record, related error in #474908: Teaser Break: IE8: JavaScript error. That fix must not break IE6/7 again.
Comment #14
abz789 commentedHey guys, i was having same issue and finally managed to crack it down by placing the following code..
and then value what ever it is.
It worked for me.
FF was already working fine, its just MICRoSOFT always :)
Comment #15
twod@abz789 I fail to see how that code is related to the plugin inserting
<!--break-->comments used by Drupal to split a node's teaser and body.This issue has been fixed in most browsers for some time now, and just recently it was also fixed in IE8, are you perhaps thinking of another issue?