The forum operates in read-only mode. Please head to StackOverflow for support.

Mon, 06/06/2005 - 14:25

fredck

Joined: 19/01/2007

Posts: 898

POLLING: Always produce XHTML on 2.0 Final

Hello Community,

The XHTML processor is becoming a key part of the editor not only to generate XHTML 1.0 compatible code, but also to remove temporary attributes and make corrections in the HTML generated by IE and Gecko.

Actually, today, if you disable XHTML (in the config file), you could have strange things in the final HTML.

I'm thinking on removing the configuration option to disable XHTML and force the editor to always produce XHTML.

So, I'm here to ask you: What do you think about it? Do you see any problem on it?

Even a message with only "OK" in the body is enough.

Thanks in advance,
FredCK

Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn

Tue, 05/31/2005 - 07:01

mcukstorm

Joined: 05/06/2005

Posts: 126

RE: POLLING: Always produce XHTML on 2.0 Fina

I think this is fine, all my sites are now designed using XHTML so if the editor only produces this so much the better.

Cant imagine why anyone would have a problem with XHTML only (however i could soon be proved wrong)

Tue, 05/31/2005 - 07:09

bnoblet

Joined: 29/11/2006

Posts: 179

RE: POLLING: Always produce XHTML on 2.0 Fina

Previously I've only not used XHTML mode to get around certain bugs ... however if those bugs are all fixed I'm happy to see this happen.

Tue, 05/31/2005 - 07:13

kanngard

Joined: 31/03/2005

Posts: 2

RE: POLLING: Always produce XHTML on 2.0 Fina

+1

- Johan Knngrd
johan AT kanngard DOT net
http://dev.kanngard.net

Tue, 05/31/2005 - 11:39

cujo_34

Joined: 08/06/2005

Posts: 20

RE: POLLING: Always produce XHTML on 2.0 Fina

I haven't been around long enough so doubt my opinion matters but I see having it XHTML only as good. XHTML is the standard now and people should be used to it etc. If there were minor bugs found in it (like the one with Firefox outputting <b> instead of <strong>) that's okay. As basically that turned out to be more of Gecko problem I believe and the fix for now was pretty simple using regular expressions etc.

I'm not aware of any other bugs but if they are worked out. Why not do the switch.

Long story short: OK.

Tue, 05/31/2005 - 12:39

reywob

Joined: 04/07/2005

Posts: 4

RE: POLLING: Always produce XHTML on 2.0 Fina

ok go for it. So long as it's backwards compatible XHTML aka <br /> instead of <br/>

Tue, 05/31/2005 - 13:48

miker99

Joined: 01/10/2005

Posts: 63

RE: POLLING: Always produce XHTML on 2.0 Final

we've had it set to true since moving to version 2 a few months ago and so don't see any problem

Tue, 05/31/2005 - 16:12

sroussey

Joined: 28/06/2005

Posts: 17

RE: POLLING: Always produce XHTML on 2.0 Fina

Tue, 05/31/2005 - 17:05

mattrobertson

Joined: 06/05/2005

Posts: 78

RE: POLLING: Always produce XHTML on 2.0 Fina

Set it to True by default and leave it as an option for someone if for someone if they need it. Then support development from here forward with it set to ON.

I have nothing against xhtml-only on the face of it but I can't help but think that when this thing gets released into the wide world some important user somewhere might and killing the ability to shift back in an emergency could be a problem.

Tue, 05/31/2005 - 20:39

#10

xenden

Joined: 08/04/2006

Posts: 321

RE: POLLING: Always produce XHTML on 2.0 Fina

S'all right by me. I like what Mr. MR said, leaving it as an "unsupported" option, but if it's too much overhead, NIX da beach.

Life's a beach and then you dive
--old skydiving shirt ;-)

Thu, 06/02/2005 - 12:30

#11

sirkalashnikov

Joined: 02/06/2005

Posts: 2

RE: POLLING: Always produce XHTML on 2.0 Final

OK with me

Thu, 06/02/2005 - 22:51

#12

bnoblet

Joined: 29/11/2006

Posts: 179

RE: POLLING: Always produce XHTML on 2.0 Fina

Please see my post here:

https://sourceforge.net/forum/forum.php ... _id=379487

about a bug with XHTML mode that makes me a little nervous about making it compulsory.

I currently have it turned off to get around the issue.

Sat, 06/04/2005 - 03:11

#13

m4ling

Joined: 27/03/2005

Posts: 10

RE: POLLING: Always produce XHTML on 2.0 Fina

OK - anything that helps unify Firefox and IE output is fine by me!

Mon, 06/06/2005 - 06:42

#14

weberho

Joined: 06/06/2005

Posts: 5

RE: POLLING: Always produce XHTML on 2.0 Final

Mon, 06/06/2005 - 14:25

#15

mjsminkey

Joined: 06/06/2005

Posts: 16

RE: POLLING: Always produce XHTML on 2.0 Fina

I would not be thrilled if this became required. I often have to put non-XTML compliant "fake" tags in the code that the XHTML setting tends to try and strip out. What the editor creates is not the final output to the page, it gets processed by Cold Fusion first, so I do still need that option. I've had other users complain about it messing up code they already had in place, they don't want it rewriting code that's there already, even if it isn't perfect.