Closed
Bug 153012
Opened 24 years ago
Closed 16 years ago
resultItemStart text not included in advanced search view
Categories
(SeaMonkey :: Search, defect, P3)
Tracking
(Not tracked)
RESOLVED
EXPIRED
mozilla1.2alpha
People
(Reporter: jruderman, Unassigned)
References
Details
Mozilla excludes resultItemStart when displaying advanced search results, making
list bullets disappear in the DMoz and Netscape search plugins and making raw
HTML spill with the Google Keys plugin. The Google Keys plugin uses
resultItemStart="<p><a id=".
Mozilla's behavior is wrong according to the Sherlock spec, which says that
resultItemStart "specifies a text pattern present at the beginning of each
individual item in the list of results"
(http://developer.apple.com/technotes/tn/tn1141.html).
| Reporter | ||
Comment 1•24 years ago
|
||
Forgot to say: I looked through all the search plugins that come with Mozilla,
and I don't think any besides Netscape and DMoz would be effected by this
change. For example, Google uses comments as delimiters (!!! I thought Google
was big on saving bandwidth).
Updated•24 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.2alpha
Updated•23 years ago
|
Updated•18 years ago
|
Assignee: samir_bugzilla → nobody
QA Contact: claudius → search
| Assignee | ||
Updated•18 years ago
|
Product: Core → SeaMonkey
Comment 2•17 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 3•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•