Re: disable-output-escaping

> Compliance with the standard and with the community opinion is the 
> objectives. Both are satisfied, as DOE has been marked as a bad practice 
> by the community.

Both satisfied ?? Sure?

Saying that anything has been marked bad by an entity called community 
implies that I actually respect the power and the decision of this 
community; That's true, I do. BUT... it's rude, because it also puts 
excludes me from it, creating a group which I do not belong to and trying to 
use that to convince me. At the same time, and you say "the community 
decided" you delegate the decision to this abstract entity called the 
community, which has the power. Also, you forget that opinions change over 
time.

Well, I think I'm part of the community, I think the opinion should change 
over time and I think someone made this decision alone, probably the 2 or 3 
guys that own the module.

IMHO, and with ALL DUE RESPECT, I think this decision should be 
reconsidered. I think that if MSIE implements a critical feature, we should 
implement too, even better - if it is compliant ( we don't want to implement 
m$ trash ).

DOE is an important enough feature that puts MSIE waaay ahead of mozilla, 
because correct rendering of data is the BASIC of everything. Visuals matter 
a lot, and if in mozilla the html data field that dumb-people input into the 
database render as ugly tags, than people is going to use MSIE, because 
there it renders as HTML tags... you know, simple bolt/italics/underline and 
bullets.
Tell me, how many applications allow people to do simple markup on data 
fields??? It's WAY better to allow DOE on the rendering side than to enforce 
correct input (which not always is possible) or to modify people's data by 
server parsing and fixing it ( not only this is more complex but most times 
it's just plain wrong : the computer should not do things with the user that 
he hasn't requested, neither should change data he inputted himself). Not to 
mention applications that rely on 
creating/capturing/transfering/moving/crawling 
for/manipulating/handling/insert-verb-here/ eletronic documents in different 
formats, converting to html and publishing it in websites/intranets using 
xml+xsl driven technology;  You know, most document formats are NOT 
semantic, so it's impossible a perfect automatic convertion to xml, but 
almost always exist a transformation to HTML which can be put inside a xml 
document and can be rendered with DOE.

> Please note that i'm not trying to argue; just to explain why you received 
> these responces to your problem.

I'm stubborn, I know. But I don't mean to piss anyone of.

I just love firefox and felt it was a pity that the company I work for ( a 
very large one ) decided to throw away firefox support for the product 
because it didn't have DOE; We have a large system all built with xml and 
xsl for presentation in browsers, and I personally always managed to make 
things work in firefox, but without DOE, it can't be done.

I'd love if any kind soul would reconsider it.

Best Regards,
Gabriel Blum