The Remove Paragraph Action is at http://freewayactions.com in the
Beta Box, and you can also use my CrowBar Action as a replacement for
the Markup Item you are using to insert your JavaScript code. That
Action removes any surrounding P (or other text container tag) and
relies on the inserted code to provide a suitable replacement.
Walter
On May 29, 2011, at 7:43 AM, David Owen wrote:
Is there an action to remove paragraph tags from a line or div? I
seem to has lost the one I had ~ Can’t find anything in the Actions
forge
WebYep’s “Rich Text” + CKEditor content adds its own extra
tags</
p> around its content , then Freeway add’s its own p tags around
that causing validation issues
On 29 May 2011, at 14:36, Walter Davis email@hidden wrote:
The Remove Paragraph Action is at http://freewayactions.com in the Beta Box, and you can also use my CrowBar Action as a replacement for the Markup Item you are using to insert your JavaScript code. That Action removes any surrounding P (or other text container tag) and relies on the inserted code to provide a suitable replacement.
Walter
On May 29, 2011, at 7:43 AM, David Owen wrote:
Is there an action to remove paragraph tags from a line or div? I seem to has lost the one I had ~ Can’t find anything in the Actions forge
WebYep’s “Rich Text” + CKEditor content adds its own extra
tags
around its content , then Freeway add’s its own p tags around that causing validation issues
It does not work too well, as Freeway default styles are kicking in and creating 1px text Creating more issues to fix.
Interestingly, I found a possible work around
Using
config.enterMode = CKEDITOR.ENTER_BR;
in CKEditor config.js file
This gets rid of the surrounding
tags in CKEditor ~ the downside it creates tags for line returns (like the plain text editor does in WebYep). Is this the answer to all my problems with using a rich text editor/WebYep/Freeway?
A further very important question would be…
Would this be a problem in a CMS if there are no
tags in blocks of text and only separating paragraphs?
Any comment or wisdon would be greatfully received
If there isn’t a P tag inside a container like a DIV or a TD, the
browser will infer one, and actually behave as if there is one there.
The page is still valid, with or without a P, because the spec doesn’t
require that text be enclosed in a P exclusively, only that it be
enclosed.
Walter
On May 29, 2011, at 1:54 PM, David Owen wrote:
Walter,
It does not work too well, as Freeway default styles are kicking in
and creating 1px text Creating more issues to fix.
tags in CKEditor ~ the downside
it creates tags for line returns (like the plain text editor
does in WebYep). Is this the answer to all my problems with using a
rich text editor/WebYep/Freeway?
A further very important question would be…
Would this be a problem in a CMS if there are no
tags in blocks
of text and only separating paragraphs?
Any comment or wisdon would be greatfully received
To fix this specifically, try this: Draw your text box, insert the
CrowBar, then add an option-space after it. CrowBar will figure out
that it isn’t alone on the line, and it will move itself outside the
P. It will leave the P there, so Freeway won’t check back and add that
font-size tag to the DIV. Hate that, especially. I know that (and why)
it’s there, but it still gets me every time.
Walter
On May 29, 2011, at 1:54 PM, David Owen wrote:
default styles are kicking in and creating 1px text
Yes that seems to work and validate. It does not need the option-space after it either (which creates an extra line anyway and space under the content)
David
On 29 May 2011, at 19:16, Walter Davis email@hidden wrote:
To fix this specifically, try this: Draw your text box, insert the CrowBar, then add an option-space after it. CrowBar will figure out that it isn’t alone on the line, and it will move itself outside the P. It will leave the P there, so Freeway won’t check back and add that font-size tag to the DIV. Hate that, especially. I know that (and why) it’s there, but it still gets me every time.
Walter
On May 29, 2011, at 1:54 PM, David Owen wrote:
default styles are kicking in and creating 1px text