Boris Zbarsky wrote:
> Benjamin Smedberg wrote:
> > History and bookmarks are different in this case: history is called by
> > gecko and therefore requires intense cooperation between gecko and the
> > embedder, while bookmarks doesn't.
> Except that with Places bookmark UI design decisions are affecting the
> proposed history APIs, as far as I can tell. So I stand by my point.
It is silly to expect that the UI design would not affect the APIs... what
exactly do you expect to be done differently? Trying to design "universal
APIs" to anticipate every future need does not seem reasonable or cost