-
Hi
I’ve noticed that if I format text in the “wrong” order the source tags get misplaced.
For example, if I have a block of text and I change its colour, then select part of that text and underline it, the underline is in a different (parent) colour decided by my WordPress theme because the and tags are OUTSIDE the tags.
But if I underline first, then change the colour, the tags go INSIDE the . Is this by design, or have I uncovered something?
-
-
Darn, the tags disappeared from that the UNDERLINE tags are OUTSIDE the SPAN tags in the 2nd para, and INSIDE in the 3rd para.
Hi Anadi,
You shouldn’t be putting so many elements on a single piece of text in the first place.
If you have some complex formatting you use often, it should be a CSS style which you pull from the drop down menu.
Not only that but using underlining on the web is extremely bad practice as underlining is assigned to hyperlinks.
We do our best to provide the best possible WYSIWYG editing environment but if you bang your head against the wall hard enough, you are sure to draw blood and/or fade into unconsciousness. No helmet will protect you.
Making the web work for you, Alec
Quite frankly, Alec, I don’t care if it’s bad practice or not.
If I am writing an article for my blog, and I have included a blockquote (which is automatically in italics), and I choose to change the color to blue (in most cases – it’s my blog and I might choose a different color for a different source of the quote), I may also want to underline part of that text to comment on it.
So in actual fact, the “so many elements” you referred to actually amounts to two – a SPAN and a U.
I am pretty certain that having to use them in a very rigid order to prevent them being nested incorrectly (and there are only two alternatives) is not a “feature” but an oversight.
I was reporting a find, not asking for a lesson.
Hi Doaadi,
Foliopress WYSIWYG is a business text editor designed to simplify and speed up posting for both prolific content sites and photographic sites, while maintaining best SEO practices.
It will be difficult to resolve the nesting tags issues as they are part of the core FCKeditor (they might be better in CKeditor and we are preparing the move to CKedtitor now, but probably not).
I have a lot of sympathy for those programming CKeditor on this issue. These editors are javascript so there are real limitations to what you can do. They do a great job in pushing those limits so far that we think we are working in a desktop application. But we aren’t.
The best thing you can do is create complex classes which you can use as pull downs.
Thanks for sharing your find.
