46853 - nsIURIContentListener needs to be broken in two.

Status: VERIFIED INVALID

(Core Graveyard :: Embedding: APIs, defect, P1)

Description

[Judson Valeski]

Currently there is an interception method (onStartURILoad()) and content 
listener methods. we should break them apart so an embeddor can still capture 
urls, but doesn't have to impl the consumer methods.

Comment 1

[Scott MacGregor]

i don't know who added this onStartURLLoad method. That's bogus in this
interface. Someone did it without getting module owner approval/review from me =).

They'll need to find a better home for this method.

Comment 2

[Judson Valeski]

Son of a !!!!! It was travis.

Comment 3

[Judson Valeski]

over to potts. the onstart stuff is moving into nsIWebProgressListener and will
subsequently be removed from nsIURIContentListener.

Comment 4

[lchiang]

per email with Jud, changing nsbeta3+ to nsbeta3- on all "embed" keyword bugs
since embedding changes will not be made in the mn6 branch. If you feel this bug
fix needs to go into mn6 branch, please list the reasons/user impact/risk and
nominate for rtm. Thanks.

Comment 5

[Judson Valeski]

-> mscott

Comment 6

[selmer (gone)]

So, this bug is purely for the removal of the bogus code right?

Comment 7

[Judson Valeski]

Yea, the method needs to be pulled from nsIURIContentListener and the equivelent
notification needs to happen via another interface (likely
nsIWebProgressListener). The tough part is going to be capturing the same
notificaiton point elsewhere, that the uri loader is able to capture.

Comment 8

[Paul Wyskoczka]

Updating QA Contact

Comment 9

[Judson Valeski]

-> 091

Comment 10

[Judson Valeski]

killing this. after talking w/ mscott, we need to keep this method here so it
can remain part of the content listener parentage chain.

Comment 11

[Michael Dunn]

Correction: Changing QA contact for the Embed API bugs to David Epstein.

Comment 12

[David Epstein]

verifying as invalid, nsIURIContentListener is intact.