[kupu-dev] why does kupu switch to "no style" rather than"normal" on a new line after a heading?
Jon Stahl
jon at onenw.org
Fri Dec 29 22:43:30 CET 2006
> -----Original Message-----
> From: kupu-dev-bounces at codespeak.net
> [mailto:kupu-dev-bounces at codespeak.net] On Behalf Of Duncan Booth
> Sent: Friday, December 29, 2006 1:23 PM
> To: kupu-dev at codespeak.net
> Subject: Re: [kupu-dev] why does kupu switch to "no style"
> rather than"normal" on a new line after a heading?
>
> "Jon Stahl" <jon at onenw.org> wrote:
>
> > I suspect there may be a good-but-not-obvious reason for
> this, but I
> > can't help but wonder why the following behavior occurs,
> and if it can
> > be modfied:
> >
> > When set a line to "heading" or "subheading" format, then
> hit "enter"
> > to start a new line, the style for the next paragraph
> becomes "no style"
> > rather than "normal". That seems very unintuitive. Worse,
> it often
> > seems to result in content authors creating lots of unstyled
> > paragraphs, which under Plone's default styles looks really weird
> > because the leading of "no style" paragraphs is much
> tighter than "normal"
> > paragaphs.
> >
> > Is there anything that can safely be done to make the next
> paragraph
> > after an <h> style be "normal" style?
> >
>
> I know, but I'm not sure there is much I can do about it.
> Kupu used to try to ensure that everything you entered was
> inside a paragraph (i.e. Normal style), but that hit problems
> at the end of the buffer when interactions with Firefox's
> attempts to insert <br/> at the end of the buffer but not
> inside a paragraph resulted in infinite loops of kupu vs
> Firefox. I changed it to just accept what the browser did
> which is why you now get the 'no style' effect.
>
> Perhaps there is a better way to handle it, but if so I
> haven't yet found it.
I suspected something like that. Would looking at how other WYSIWYG
editors such as FCK or HTMLArea/Xinha be likely to offer some
inspiration? It seems like this would be a common problem, yet I don't
think it afflicts other editors.
best,
jon
More information about the kupu-dev
mailing list