Closed
Bug 862688
Opened 12 years ago
Closed 12 years ago
functionality of data: protocol for custom forms in keyword.URL when searching from awesomebar is gone
Categories
(Firefox :: Search, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mardeg, Unassigned)
References
()
Details
(Keywords: regression)
bug 738818 being fixed means only OpenSearch engine searches now happen from the address bar, and I have a feeling the format of these engines doesn't allow for non-domain URLs like data:text/html
An example is in the URL field. It's a POST to startpage with search results customised with the "prf" input. A matching search engine with the same preferences of results can of course be created (when bug 862401 is fixed), so such an edge case is likely WONTFIX.
I just filed this because I may not be the only one who lovingly customised keyword.URL this way.
OS: Windows XP → All
Hardware: x86 → All
Version: Trunk → 23 Branch
Comment 1•12 years ago
|
||
(In reply to Mardeg from comment #0)
> bug 738818 being fixed means only OpenSearch engine searches now happen from
> the address bar, and I have a feeling the format of these engines doesn't
> allow for non-domain URLs like data:text/html
Indeed, this isn't currently supported.
> An example is in the URL field. It's a POST to startpage with search results
> customised with the "prf" input. A matching search engine with the same
> preferences of results can of course be created (when bug 862401 is fixed),
> so such an edge case is likely WONTFIX.
Indeed, this is WONTFIX, for the reasons you state!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•