Subj : Re: How can JS intercept relayout calls?
To   : netscape.public.mozilla.layout,netscape.public.mozilla.jseng
From : Geoff
Date : Thu Dec 23 2004 11:22 am

Mike Shaver <shaver@mozilla.org> wrote in
news:cq9l4q$c022@ripley.netscape.com: 

> Geoff wrote:
>> It looks like I'm just going to get in a cycle of "no, don't ask us,
>> ask /them/".  The DOM folks can say that it's not their issue since
>> there's no DOM event that will do what I need.  The Layout folks can
>> do just the opposite what's happening here and say they only deal
>> with layout, not the Javascript side of things.
>> 
>> Nonetheless, there's somewhere the JS Engine and the Layout engine
>> meet, and that's the bit I wanted to find out about.
> 
> No, it's not.  The JS engine and Layout meet in XPConnect, which is a 
> mostly-generic mapping between XPCOM and JavaScript.  What you are 
> asking about is a DOM/layout issue, as Neil and Brendan have tried to 
> tell you.  The JavaScript engine doesn't know whether it's scripting
> the DOM or a VXML IVR system; it just deals in script execution and
> objects. 
>   If the layout system's DOM provides the capability you are looking 
> for, the JS engine will reflect it happily and without any knowledge
> of the specifics of the capability.  If it does not, nothing in the JS
> engine can help you.  Thus: take it up with the layout and DOM people.

I'd like to apologise.  I'm sorry.

I posted what I thought was a proper question in the proper newsgroup,  
Brendan's short, sharp reply came across to me as rude and arrogant, as well 
as wrong.  It looked as if he hadn't read or understood the message.  Still 
looks like that, in fact.

However, just because he appeared rude and ignorant was no excuse for me to 
do so.

> 
> DOM people who send you back to the JS engine group for the question
> you asked will be dealt with sternly!
> 
>> But I think I'll give up before I annoy even more people.  I'll stick
>> with things being broken in Mozilla because that's easier than trying
>> to find out how to fix it.
> 
> Three experienced Mozilla developers, including myself, have now tried
> to tell you where to go to find out how to fix it.  Don't blame 
> "Mozilla" for the fact that you won't listen to the advice and 
> instruction you're given.

The DOM group still seems to me to be the wrong (or at least 
counterintuitive) place for me to post that question, although I take the 
point that Layout may be appropriate.  I stand corrected.  I'm happy to take 
your word for it, but in all honesty I can't see me trusting Brendan's word 
on anything, now or in the future, no matter how experienced he may be.

Also, to try to put an end to this part of the thread, it's not a flagrant 
violation of nettiquette to change the followup if you believe what that the 
person who did it was wrong.  I did (and in Brendan's case still do) believe 
that.  And yes, I'm posting this message to both newsgroups because I believe 
the apology should appear in both.

Many thanks for your patience,

    	    	    	Geoff

.