hi everyone,

I'd like to ask you something about the WYSIWYG.

It seems that in WYSIWYG mode, the ENTER key leads to jump a lign ... as between those 2 sentences. I heard it was a WYSIWYG limitation, because of its spacing's width. 

If it's right, is there a way to bypass this limitation ?

Thank you for thinking about it and please forget me for this frenglish, i guess it wasn't really well said.

Edgard

With IE when you hit return the IE Rich Text Editor places in <p> tags giving a line space when you hit return, but if you hit SHIFT -> Return it puts in a <br> and only jumps by one line. Maybe Microsoft will change this in future versions of IE.

In Mozilla and Netscape 7.1 the WYSIWYG editor only moves by 1 line when you hit return as the Rich Text Editor has been implement differently in these browsers.

thank you -boRg-, i successfully test Shift + Return.
But this tip isn't really handy for common user (maybe i'm wrong  ) ... i may keep the classic editor (divided in Basic or Prompt), because i've got a lot of Macintosh users on my forum, the WYSIWYG editor didn't work with, even with IE (but i wonder with Safari, the apple's browser) ... and it's the same with Opera.

Finally, as usual, it's a pity each browser uses different implementation. Rich Text Editor implement should be identical, whatever the browser is.
Did you try the WYSIWYG editor with Amaya ? This browser ( http://www.w3.org/Amaya/ - http://www.w3.org/Amaya/ ) is made by the World Wide Web Consortium which *tries* to standardize internet rules.

Edgard 

edgard wrote: but i wonder with Safari, the apple's browser

I just test, it can't use the WYSIWYG editor, as IE for Mac.

Microsoft have not implemented the Rich Text Editing features in the Mac version of IE, but Mozilla 1.3+ and Netscape 7.1 have implemented it across all platforms. Other browsers such as Opera, Safari etc. are yet to implement Rich Text Editing.

MadDog some of the PHP forums that use WYSIWYG editors don't use the standard built in editor in the browser, instead they implement their own from scratch which is why they work differently.

If you can find away around the two line thing then please let me know, but I have spent days looking into it with no avail.

I think my question runs along the same vein as these have...

I'm using a Mac and Safari to access this message board. When I submit
anything from the Post Reply or New Post text box it places a BR at the
end of each line in the input box rather than letting the text wrap
normally to the end of the displaying table.

This should be evident in seeing how this post is being displayed
compared to others. Does anyone have any clue why this is happening or
what I can do to prevent it from happening?

---edit ----

i have deleted the check bit you added above ok.

and have also deleted your last post which stated the above.

---edit ----

-boRg- wrote: I don't want to, I want to keep to the WW3 standard for Rich Text Editing, this way as more browsers become Rich Text Enabled they can also easily use the WYSIWYG editor without to much alteration to the code. Which is why the one on this site is the only multi platform, and multi browser WYSIWYG editor within a forum system.

bruce im not sure but would be able to use javascript to look at the source and if they put <p> it changes it to <br>... i know that people would say what about if you want to write <p> but that would be &lt;p&gt;  ...

i say use javascript as you require it anyway to use the features.

this is jusy an idea... ill keep looking

There's a WYSIWIG editor called htmlarea at http://www.interactivetools.com/iforum/Open_Source_C3/ - http://www.interactivetools.com/iforum/Open_Source_C3/

One of the mods was to replace the <P> tags with <br>. Javascript IIRC. One of the problems was that is screwed up lists as each list item ends in a hard return.

I always thought something could be done with css by using a different paragraph class for rte paragraphs. You could specify a different bottom-margin for those paragraphs. Might not show within the rte, but could show on the post page at the least.

Something else for the "One-of-these-days" list