[Webkit-unassigned] [Bug 27434] adding necessary functions and properties to Document IDL gobject bindings

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=27434





--- Comment #20 from Mark Rowe (bdash) <mrowe at apple.com>  2009-07-30 11:44:56 PDT ---
(In reply to comment #18)
> > >  so - sorry, but utilising some quotes "existing" quotes API that isn't
> > > actually the DOM isn't acceptable.  forcing people to write code that makes
> > > exceptions for webkit, by having a non-standard, non-DOM-based version of the
> > > API is _not_ a good enough reason to turn down a review.
> > 
> > An application using WebKit by definition has to make use of WebKit-specific
> > API.
> > 
> 
>  sorry, but you've completely lost me.
> 
>  i thought we were discussing the definition of the webkit-specific API.
> 
>  please correct me if i'm wrong, but it sounds like you're saying that the
> webkit API is set in stone, and that anyone wishing to make use of webkit must
> live with that, even if it doesn't do what's actually needed.
> 
>  ... but i doubt very much that that's what you're saying.

That would be a stupid thing for me to say.  Thanks for suggesting that it was
what I said.

You were arguing that it is vitally important to expose this incomplete DOM
binding immediately, even though the same information (the URL of a document)
is exposed via the WebKit API in a different manner.

My point is simple: I don't see the value in exposing an incomplete DOM binding
for this property since there is an existing means of retrieving this
information.  It doesn't seem worth the mess of #if'ing up the IDL files and
the confusion that would result from users who expected the exposed properties
to behave in the standard manner.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.