respect custom styles in fullscreen mode

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614

[i-just]

Description

All the Custom Styles provided in the field’s configuration are automatically wrapped in an ID that references the field’s handle (e.g. #fields-input-ckeditor-myCkeditorField if the field’s handle is myCkeditorField). This ensures that if you have multiple CKE fields on a single page that use different styles, those styles are applied only to the relevant editor areas. (https://github.com/craftcms/ckeditor/blob/5.6.1/src/Field.php#L1876)

When you enter a fullscreen mode, CKEditor appends a new container to the body element and copies the editor in there - only the editor, not the surrounding wrappers, so that ID is no longer applicable, which causes the custom styles to be ignored.

Fix: add the same identifier to the fullscreen mode container (but this time as a class), ensure that any custom configuration that the user might have provided for the fullscreen feature is still respected and add that class qualifier to the Custom Styles wrapper.

Related issues

#614