We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket History
Next Change →

Changes between Initial Version and Version 1 of Ticket #750

Timestamp:

Jun 25, 2007, 4:55:30 AM (18 years ago)

Author:

Martin Kou

Comment:

I'd like to see this fixed as well. Any plans to fix it soon?

Moved from SF. Original poster: lizl

Yes, fckeditor definitely supports inline styles. I implemented a workaround to the above problem by stripping out the comment tags before passing the content to the editor, but it would be preferable if the editor handled the comment tags cleanly.

Moved from SF. Original poster: severy

does fckeditor support <style> at all? I assume not

Moved from SF. Original poster: liuspider

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #750
- Property Reporter changed from Martin Kou to severy@…

Ticket #750 – Description

-                      initial
+                      v1
 example of this with the following HTML:
+{{{
 <style type="text/css" media="screen"><!--
 p {
 …
 color: black }
 --></style>
+}}}
 In the web browser, the above style definitions work