Changes between Initial Version and Version 1 of Ticket #8406, comment 3
- Timestamp:
- Sep 28, 2011, 6:55:25 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #8406, comment 3
initial v1 1 Styles from contentsCss won't work in fullPage mode by Design. The problem is that they are applied to styles dropdown which confuses users. This is a bug but is covered by #7735. **This part is a duplicate.**1 Styles from contentsCss won't work in fullPage mode by Design. The problem is that they are applied to styles dropdown which confuses users. This is a bug but is covered by #7735. 2 2 ---- 3 3 … … 16 16 }}} 17 17 18 And inside edited pageinsert a link pointing to mystyles.css file:18 and inside edited page, insert a link pointing to mystyles.css file: 19 19 {{{<link href="../mystyles.css" rel="stylesheet" type="text/css" />}}} 20 Which contains:20 which contains: 21 21 {{{ 22 22 h2.red{ … … 30 30 Probably some dynamic styles loading for styles dropdown would be needed. 31 31 32 This part is valid and it has worked that way from CKEditor 3.0 (stylesSet was introduced in CKE 3.3. Before stylesCombo_stylesSet was used) 32 33 34 Just to sum up:[[BR]] 35 #7735 - is a bug in which styles from contentsCss are applied to drop-down list but not to editor content area. 36 37 This bug - #8406 - is a is a feature/bug in which styles, attached to head section of edited page are applied to editor content area but they are not dynamically applied to editor drop-down list event if this drop-down is using styles from such file. 38
