Forum closed. New forum available at

0.2 dev version and Firefox 2.0 :: new-paragraph issues

Discuss features, code, contributions, ideas, suggestions, ...
For bugs, patches and feature requests, please post on the Trac:

0.2 dev version and Firefox 2.0 :: new-paragraph issues

Postby gustav vella on Sun Oct 29, 2006 10:37 pm

Salut JF - je me debrouille en Francais ... mais en Anglais c'est plus facile ...tant pour moi et pour le reste .. quand meme je te félicite en Francais come il faut :))... et en anglais...

..First of all I have to day that this is simply neat and unique - great thanks!!

I'm having some trouble with 0.2 dev in Firefox2.0 - when I open a new document and want to set the first paragraph I do so using the menue - but it's only when I start typing that the visualization of the paragraph section is actually activated. Alternatively, as a workaround, I could move the cursor back an forward and the see the paragraph block.

Should the editor by default give me an empty paragraph section on opening a new document?

There is also a situation where you cannot access the paragraph block via the mouse - after some time I found out that moving the back and forward cursor keys you can access the paragraph.

I also had the situation (although I can't reproduce it consistently) where leaving an H1 section by pressing the enter key, you don't get a <p> but an <H1> again.

Are these issues known? Am I possibly misunderstanding the default behaviour of the editor? On your blog you discuss new 0.3 Version in a posting which is 4 weeks old - in trac you have an 0.3 branch with changes 2 days could you point out the changes?


salut de Cologne (Allemagne)

gustav vella
Posts: 1
Joined: Sun Oct 29, 2006 9:33 pm
Location: Germany

Postby jfh on Mon Oct 30, 2006 10:36 am

Salut Gustav, et merci pour tes encouragements ;)

Well, Gecko's default behaviour is to allow editing directly in the <body>, so without a container (like P). This isn't XHTML 1.0 strict compliant, so you can see in wym.js code that I've added:
Code: Select all
if(container.tagName.toLowerCase()=="body") execCom("formatblock","P");

This code is executed at the keyup event, so when you start typing.
I didn't found a better way to fix this issue, but you can for example set the default body value to <P>&nbsp;</P> (in the div and in the iframe).

About the H1 issue: are you sure you didn't press shift+enter ?

0.3 branch is still very experimental. I think WYMeditor will become a jQuery plugin, but I need more testing to answer your question...
User avatar
Site Admin
Posts: 370
Joined: Sat Sep 23, 2006 8:43 pm
Location: Belgium

Empty Tags cause erronous behaviour

Postby Dyflexis on Wed Nov 08, 2006 5:48 pm

Hello JF,

When starting with empty tags (<p></p>, for instance) there's no possible way of inserting any text inside it, although it the tag does show. The caret is placed at the right inside the paragraph container.

How to reproduce this:

Place an empty tag in de contentEditable div in the editor.html file.
Posts: 5
Joined: Wed Nov 08, 2006 11:11 am
Location: Den Haag, Netherlands

Postby jfh on Thu Nov 09, 2006 1:27 pm

OK, thank you Dyflexis.
Sorry Gustav, I didn't correctly understand what you meant.
I'm not sure, but I think this is due to Gecko's behaviour (should I say bug ?).

You can check the bug fix at the Trac, or update your svn working copy.
User avatar
Site Admin
Posts: 370
Joined: Sat Sep 23, 2006 8:43 pm
Location: Belgium

Postby Daniel_R on Fri Nov 10, 2006 11:47 pm


It's not a bug in Firefox since both HTML and CSS standards specify that if a block element is empty, it should not be rendered at all.

I believe it's what causes this problem.
Posts: 10
Joined: Wed Sep 27, 2006 12:19 pm

Return to Developers

Who is online

Users browsing this forum: No registered users and 1 guest