Firefox has a flaw that was introduced in a patch (see http://forums.mozillazine.org/viewtopic.php?f=9&t=1991855) in which non-standard properties in the markup are stripped when using design mode. This results in all of the data that identifies the image, format, view mode, etc. not being preserved when switching from rich text to plain text, and also has the effect of saving the node without enough information for the the image markup to be rendered when viewing the node.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 917212_2.patch | 6.14 KB | paul.lovvik |
| #1 | 917212_1.patch | 6.14 KB | paul.lovvik |
Comments
Comment #1
paul.lovvik commentedHere is a patch that works around this problem by stuffing these custom image attributes into the class field in the markup. This is done in a way that the data can be preserved, but it doesn't affect the special markup that represents the image in the node body, so this change does not affect the rest of the system.
Comment #2
paul.lovvik commentedMinor documentation fix.
Comment #3
AlexJ commentedIs there a patch I can use with D 6.19, and Insert that will solve this problem?
Comment #4
JacobSingh commentedThere is no 6.x version of media anymore.
Comment #5
james.elliott commentedThis is hideous. But it's necessary and it works. Barring some major housekeeping in the JavaScript of the module, this is the best solution that completely addresses this specific issue.
Setting to needs review so that the test can show that it applies cleanly. If so, I'll commit it.
Comment #6
james.elliott commentedCommitted
Comment #7
james.elliott commentedComment #9
Pedro Lozano commentedI opened an issue for some problems introduced by this patch: #1332500: Alt text doesn't work from wysiwyg