>I have a stylesheet with <textarea> and <div> tags, when they are >empty, xalan outputs <textarea/> and <div/> instead >of <textarea></textarea> and <div></div>, which Internet Explorer >doesn't correctly interpret....Is it because xalan doesn't know >about IE's bug on <textarea/> and <div/>, so it thinks it >can safely output that?
Of course it can safely output that, since the XSLT spec has a bunch of 'may/should' statements in it's HTML output section, which is what we follow. This is an issue with IE, not with Xalan or the XSLT spec. (Sorry to sound so harsh, but this is an important point - we really do try to get the best possible compliance with the XSLT 1.0 spec itself. Unfortunately, in some cases like yours, the XSLT spec is not optimized or even compatible with the real-life HTML software you use that has clear bugs or non-spec compliance issues. Also remember that there are plenty of Xalan users who don't care a bit about HTML since they're doing strict XML processing or the like.) > > Generally, Xalan doesn't know about any browser-specific issues. > > Do people want separate serializers for every version of every > > browser? I definitely understand the need of some users to have customized output for specific browsers, including browser versions and bugs in those products. The bad news is there's only a limited number of active committers right now, and most of them are focused on strict XSLT, performance, and bug questions. The good news is remember that we're open source! If someone wants to build browser-custom serializers they're very welcome to do it, and if they're popular, we'd even be happy to check them in. - Shane ===== <eof aka="mailto:[EMAIL PROTECTED]" "http://www.otnemem.com/"=.sig /> __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
