On Mon, 18 Jun 2001, jesus X wrote:
>
> Ian Hickson wrote:
>> (Where Gecko is the rendering engine (HTML, CSS, DOM, etc) and Mozilla
>> is the web browser.)
>
> Is not the DOM, while part of Gecko, partially connected to the UI as
> well?
No more so than HTTP or CSS.
> IIRC, for interfacing with users, the DOM has to go through the UI's
> set of controls, correct? Or am I adding links where there are none? :)
The DOM is the Document Object Model, namely the interface by which a
script speaks with the document. Only a few minor parts of the DOM
actually involve UI. The window.alert() method would be one such example.
It needs to be implemented by the embedding application (KM, for instance)
if JavaScript alerts are to work correctly.
This is similar to the fact that HTTP needs its password dialogs
implemented by the embedding app in order for HTTP authentication to
function correctly, and that the rendering and selection code (which
theoretically falls under the CSS flag) needs the embedding app to
implement drag and drop if that is to work.
(Note. I'm no embedding expert, so take some of this with a moderately
sized grain of salt please!)
--
Ian Hickson )\ _. - ._.) fL
Netscape, Standards Compliance QA /. `- ' ( `--'
+1 650 937 6593 `- , ) - > ) \
irc.mozilla.org:Hixie _________________________ (.' \) (.' -' __________
