[SS] Some style definitions should be blocked in the combo

[deadmoroz@…]

When displaying styles available from fckstyles.xml in styles combo each option is being styled according to the style it belongs to.

But if the style has something like "padding-left" attribute, let's say 180px, then the option becomes invisible (the padding is applied to the combo's option as well and it's being displaced completely to the right).

It's needed to introduce some !important attributes for combo's options that couldn't be overriden by styles from fckstyles.xml

---

Moved from SF:
​http://sourceforge.net/tracker/index.php?func=detail&aid=1392114&group_id=75348&atid=543653

[Martin Kou]

Marked it as [SS] (Style Selector).

---

Moved from SF. Original poster: fredck

[Frederico Caldeira Knabben]

I was doing some tests with it. It could be "solved" by changing the following rule to the fck_editor.css skin file"

.SC_Item *, .SC_ItemSelected *
{
	margin: 0px !important;
	padding: 0px !important;
	text-indent: 0px !important;
	clip: auto !important;
	position: static !important;
}

But then, came to my mind that it may be important in some cases to leave some of those properties untouched for a proper and more realistic preview. For example, there could be a style that adds a border to the selection, with a small padding to it. If we remove the padding, the style could result ugly in the preview.

There is also another aspect to consider. Currently it is possible to "correct" it by adding the above CSS definition in the editing area stylesheet. So, it is already possible to a developer to fix those things if necessary.

I'm a bit unsure about the correct approach here. For now, I'm postponing it to the 2.6.1, so we can take the final decision later, maybe based on further discussion over it.

[Martin Kou]

After some discussion with Fred yesterday, it was decided that the style overrides are better done by the user instead of by us. However, we should leave some hints in the editor/css/fck_editorarea.css and in our ​documentation page so that our users will know how to handle that.

[Frederico Caldeira Knabben]

The new comments look good.

If the comment style are to be fixed in lines 53-55, for consistency it should be done in all comments in that file. Otherwise, just use the style previously used.

Also, the comment style correction at line 53-55 left the comment closing not aligned at line 56.

[Martin Kou]

Fixed with [2138].

Click here for more info about our SVN system.