I feel this issue is quite critical, at the moment, as it makes any editor not usable when making tables in Internet Explorer 7+.
While creating or editing a table into a node in Internet Explorer 7+, once the page is saved, there is a large amount of empty p and br tags added at the top of the node. This only happens in Internet Explorer 7+. But when editing the node in any browser, including any IE, the additional p and br tags are NOT visible.
I have tested this in CKeditor, FCKeditor and TinyMCE. I used this with the minimal required modules to have the WYSIWYG module working with an editor. The issue cannot be duplicated in any other browser but the Internet Explorer range of browsers.
Comment | File | Size | Author |
---|---|---|---|
#18 | toolbar.jpg | 19.11 KB | ju1i3 |
Comments
Comment #1
TwoDThis sounds like a problem with the editors themselves, or if the tags are only visible on a viewed node - but not in the source when creating/editing it - it's an input filter problem. Can you provide exact steps to reproduce this when Wysiwyg modules is used that do not have the same effect in the official editor demos?
I'm not able to reproduce this myself in IE8.
I do sometimes get a
<p> </p>
placed before the table depending on where I insert it and if I hit enter before doing so. But I expected that as pressing enter means create a new empty paragraph, and then the table is inserted after it.The minimal required modules to get an editor working would just be Wysiwyg module itself, it does currently not depend on any other Drupal module.
http://ckeditor.com/demo
http://tinymce.moxiecode.com/examples/full.php
Comment #2
triversedesigns CreditAttribution: triversedesigns commentedHi TwoD,
Exact steps are as follows:
Install Drupal Core
Upload and Install WYSIWYG module
Upload editors to libraries folder (TinyMCE, CKeditor, FCKeditor)
Assign Editors to Input Filters
Edit assigned Editors buttons and set css to use editor default css
Create a node with a table
Save Node
Thats when it all works fine, but doing so in IE 7+ gets that same issue. I have had this happen over a number of sites recently, and even on a vanilla install of Drupal with just WYSIWYG module.
Comment #3
triversedesigns CreditAttribution: triversedesigns commentedNote: I also have tried with and without JS and CSS compression enabled and have had the same result.
Comment #4
TwoDI still don't see any p or br tags if all I do is add a table. Do they show up if you disable the editor after adding the table? If not, it's not a problem with Wysiwyg module or the editor, as that's what'll be submitted to the server and stored in the database.
What buttons did you enable? Did you try with all buttons unchecked so the editors return to their default state?
The CSS setting should not make a difference as all it does is change which stylesheets will be included in the editing area. It doesn't change how the editor behaves or what the rendered node will look like.
Comment #5
triversedesigns CreditAttribution: triversedesigns commentedI installed a vanilla instance of Drupal again with WYSIWYG and FCKeditor and CKeditor. I assigned the editors to each input format (defaults, Filtered and Full HTML). Changed nothing, so should load default editor buttons as you described above.
After doing this and trying IE7 all worked completely fine. So I went back and edited the buttons that are available via the Buttons and plugins section and enabled some buttons but not others. Tried again in IE7 and I got the addition of the p and br tags. I have also noticed in the source that the br tags are placed at the end of each table property such as td, tr, table, etc.
I then tried editing the page in IE7 and disabling the the rich-text and submitted again, which resulted in the same output as if the rich-text was enabled.
Comment #6
TwoDWhich exact buttons did you enable when you got the extra tags? Was the Teaser Break button one of them?
Comment #7
triversedesigns CreditAttribution: triversedesigns commentedYes it actually was, I disabled it and now the page is rendering correctly.
Comment #8
TwoDSounds like this is a problem with how Teaser Break handles the content then (by passing it via jQuery/the browser). We're dealing with that in #510552: Invalid XHTML: missing trailing slashes, absolute urls and uppercase tags.
Comment #9
mshepherd CreditAttribution: mshepherd commentedThe patch at that issue does not fix this table rendering problem.
Comment #10
krizon CreditAttribution: krizon commentedI have the exact same problem as described by triversedesigns in IE7 and IE8 using TinyMCE as editor. I do not have the Teaser break button enabled.
Page saved in IE8:
http://www.teckelclub.nl/node/82
Same page saved in Chrome:
http://www.teckelclub.nl/node/83
Comment #11
TwoD@krizon, do you have any other plugins provided by other Drupal modules enabled? The issue in #510552: Invalid XHTML: missing trailing slashes, absolute urls and uppercase tags isn't specific to Teaser Break but to the way it treats the source code. Other plugins do the same thing so I've tried to provide them with a different way of doing things that isn't as invasive in that issue (available for D7 in the xhtml_callback branch).
Comment #12
sunComment #13
myphi CreditAttribution: myphi commentedSame problem with TinyMCE 3.4.7. Really still no solution?
Comment #14
TwoDPlease don't change the issue status unless you can provide more info or answers to the previously asked questions.
I've been unable to reproduce this issue with the setup I've got, so I need to know more about the editor configuration.
Comment #15
jchambers2012 CreditAttribution: jchambers2012 commentedI just setup for our new internal webportal for our company and is having the same issue in IE9/Win7. Please let me know if you need more info.
Drupal -> 7.15
IMCE -> 7.x-1.5
CKEditor -> 7.x-1.6
IMCE Wysiwyg API bridge -> 7.x-1.0
Wysiwyg ->7.x-2.1
TinyMCE 3.5
Button enabled:
Bold
Italic
Underline
Strike-through
Align left
Align center
Align right
Justify
Bullet list
Numbered list
Outdent
Indent
Undo
Redo
Link
Unlink
Anchor
Image
Clean-up
Forecolor
Backcolor
Superscript
Subscript
Blockquote
Source code
Horizontal rule
Cut
Copy
Paste
Visual aid
Remove format
Character map
Help
Advanced image
Font size
Table
IMCE
Teaser break
Comment #16
TwoD@jchambers2012, The original post says it happens with all editors.
You should really not be using Wysiwyg module together with CKEditor module though, they will both try to control the CKEditor JavaScript library and it can lead to unpredictable results.
Please disable CKEditor module if you'd like to continue using Wysiwyg module and see if that makes a difference. I don't think it'll make a difference to TinyMCE, but maybe it could be the cause if having both modules loading the CKEditor library causes a JavaScript error that interferes with other scripts.
Comment #17
ju1i3 CreditAttribution: ju1i3 commentedOne of my users is having this problem (she will insist on using IE!) I don't have the CKEditor Drupal module but I do have the CKEditor program (CKEditor 3.5.3.6655).
My toolbar is below
I can give you access to the relevant site if you want.
Comment #18
ju1i3 CreditAttribution: ju1i3 commentedHere's the toolbar
Comment #19
ju1i3 CreditAttribution: ju1i3 commentedComment #20
TwoDSorry for not getting back sooner.
I still can't reproduce this issue. I only have IE8 to test with right now, but I'll try older versions again when I get home from work.
I also can't find anything odd with your configuration based on the information you provided. Access to a site where this can be reproduced would be helpful, if you're still interested.
For now, I can only mark this "cannot reproduce". :(