#9694 closed Bug (invalid)
config.contentsCss not working in inline editing
| Reported by: | giammin | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | 4.0 |
| Keywords: | Cc: |
Description
content.css is ignored when editing inline
i tried to set config.contentsCss to another file but it is ignored anyway
Change History (2)
comment:1 Changed 13 years ago by
| Keywords: | contentsCss inline removed |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
comment:2 Changed 12 years ago by
While the inline editor is intended for working directly on final pages, I don't view it as improbable that a CMS may wish to use it as well on their backend. If a decision were made to provide support for custom content CSS in inline editors, you could use (once the scoped attribute has more support):
<style type="text/css" scoped>@import url('custom.css');</style>

contentsCss is used with iframe editor and not with inline editor.
With inline editor you are editing content directly on HTML page. This content is using HTML page styles.