Open
Bug 233425
Opened 22 years ago
Updated 3 years ago
Allow protocols and extensions to register supplemental fixup objects.
Categories
(Core :: DOM: Navigation, enhancement)
Core
DOM: Navigation
Tracking
()
NEW
People
(Reporter: jtalkington, Unassigned)
References
(Depends on 1 open bug)
Details
User-Agent:
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040207 Firebird/0.8.0+
This is kind of an offshoot of bug 202196. We should allow protocols and
extensions to register with the fixup interface, allowing us to be more flexible
with the fixup. For example, the gopher protocol could could register a new
fixup routine that identifies host names that start with "gopher" as gopher
hosts, or an extension could be written that allows the user to map host names
to protocols via regex.
Of course, all of this would be bypassed if the user types in a correct looking
scheme, as is the behavior now.
I have no idea how to go about doing this, but I'll take ownership of the bug
and look into it. However, don't be suprised if this gets flagged helpwanted ;)
Reproducible: Always
Steps to Reproduce:
-> NEW
It sounds interesting, I think the idea would be to have something like:
"assume x hostname is the protocol y"
x could equal y, but it would also allow more flexibility.
Absent doing this locally, this could also be very easily done with a personal
Internet Keyword server...
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: adamlock → benc
Updated•16 years ago
|
Assignee: adamlock → nobody
QA Contact: benc → docshell
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•