I've been able to repro this bug on a simplytest.me install of Scald Galaxy...
Enable Breakpoints module.
Enable Picture module.
Add a few Breakpoints (/admin/config/media/breakpoints):
mobile (min-width: 0px)
narrow (min-width: 481px)
wide (min-width: 984px)
Create a Breakpoints group (e.g. Basic) and add the breakpoints to it.
Edit the corresponding Picture group (e.g. /admin/config/media/picture/groups/basic) and assign the default images styles to the different breakpoint sizes.
Edit the Scald Image rendering context for "Full Page" (/admin/structure/scald/image/contexts).
Set the Transcorder to the new picture group... e.g "basic (Picture group)" and save.
Create a new "Article" node.
Upload an image to create a new Atom.
Drag and drop the image to the Body field.
Right-click the image and change the "Context" to "Full Page" and click OK.
The image "disappears" from the editor area.
Setting the context back to a non-Picture group context "restores" the image.
The image only disappears in the node form.
If you save the node, the image will appear correctly.
This bug will make very difficult to use Scald on an adaptive site.
Comments
Comment #1
JonesUI CreditAttribution: JonesUI commentedComment #2
jcisio CreditAttribution: jcisio commentedIt's the general problem when there is JS in the textarea that requires other library on the page. Could you try to use the ContentEditable mode instead of the Iframe mode in CKEditor?
Comment #3
JonesUI CreditAttribution: JonesUI commented@jciscio
I am happy to try your suggestions, but I have not been able to find any documentation that describes how to switch CKEditor from Iframe to ContentEditable mode.
Is there a configuration line I can add under "Advanced Options" > "Custom Javascript configuration"?
Thanks!
Comment #4
nagy.balint CreditAttribution: nagy.balint commentedI followed this guide : https://www.drupal.org/node/2335627
And using the latest dndck4 widget implementation in the latest dev, and ckeditor iframe mode (which is the default) and it works fine for me.
So closing for now. Let me know if you have further questions.
Comment #5
nagy.balint CreditAttribution: nagy.balint commentedJust realized that it likely worked for me cause chrome has native picture tag support, and then it does not require any added js.
And of course in wysiwyg added polyfill js will likely not run properly.
Comment #6
DeFr CreditAttribution: DeFr at Axess Open Web Services commented@mordaga: Just in case you still need it, the line to add to Custom javascript configuration would be
config.extraPlugins = 'divarea';
And then, you need to make sure that your CKEditor build includes the div area plugin. If you do so, then, the behaviors should attach properly, and everything should work, at least when using the widget mode commited to the latest dev (using a similar setup over here).