Closed Bug 14927 Opened 25 years ago Closed 25 years ago

[FEATURE] Url Dispatching Part I

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
All
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: mscott, Assigned: mscott)

References

Details

This first stage for getting url dispatching going involves covering dispatching
urls based on protocol scheme (and not content type).

Several examples include:
1) Clicking on a url in the sidebar. You expect it to load the url in the
content webshell for the current browser window

2) You are in the browser and you click on a mailbox link. You expect the url to
get dispatched to messenger and messenger should display the url.

3) You are in messenger and while viewing a message, you click on an embedded
http link. We should find a browser instance which can run this url.
I forgot to add Bill and Radha when I filed this bug over the weekend.
Blocks: 15162
adding myself to cc: list
Blocks: 12580
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
I'm killing this bug. We've decided we aren't doing protocol based url
dispatching and going completely down the content based dispatching route.
Scott - is there a bug to track the content based dispatching route?
Oops. I forgot to reply to your question Lisa. The bug for content based
dispathcing is the one right after this one...Bug #14928
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
Status: RESOLVED → VERIFIED
verifying this as invalid - url dispatching based on content type being
implemented
You need to log in before you can comment on or make changes to this bug.