Currently, when generating the "enable/disable rich text" link, the the link is styled only with an id, and it keys off the field it points to e.g. id="wysiwyg4body" where "body" is the field in question.

Since there is no class, the only way to style this link via css is with the id selector e.g. #wysiwyg4body

In my case, I want to style this link to look like a button. Here's the css:

/*button to enable/disable tinymce rich text link*/
#wysiwyg4body{
	text-align:center;
	text-decoration:none;
	text-transform:capitalize;
	width:100px;
	display:block;
	padding:3px;
	color:black;
	border-bottom: 2px solid #848484;
	border-right: 2px solid #848484;
	background-color: #F0F0F0;
	margin-bottom:8px;
}

#wysiwyg4body{
	border: 2px solid #848484;
	border-bottom:none;
	border-right:none;
}

This works fine, but it means I need to add another selector every time we add a new field for tinyMCE. So if I have a module with a field called, say, YouTubeCode, I'll need to go back and add the selector #wysiwyg4YouTubeCode to my css. Not a big deal, but a little tedious and easy to overlook.

What I would prefer is a class called something like "wysiwyg4all" that I could then style generically for ALL enable/disable links. Then I could selectively change any exceptions with either the id selector for that particular field, or you could also inject the name of the field into the class name e.g. class="wysiwyg4all body", which I could then modify (or ignore) using the css dot syntax .wysiwyg4all.body

I hope this makes sense...

Comments

drumdance’s picture

Forgot to mention, the place where this is most problematic is on user profile fields. Our sites have a lot of open-ended questions, but they're different on every site, so it's quite a bit of work to add every one of them to each theme's css as an id.

pomliane’s picture

Status: Active » Closed (won't fix)

This version of TinyMCE is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.