The pipelining "WARNING" message really shouldn't include the phrase "experimental feature" any longer. Kevin suggested "advanced feature" instead, and I think that makes good sense. Here's his rewording (repeated here, originally from bugscape bug 17549): "WARNING: pipelining is a feature designed to improve page-load performance but is not fully supported by some web servers and proxies. This feature is for advanced users only."
Severity: normal → major
Status: NEW → ASSIGNED
Keywords: mozilla1.0.1, nsbeta1
Priority: -- → P2
Whiteboard: [adt2 RTM]
Target Milestone: --- → mozilla1.0.1
Comment on attachment 92775 [details] [diff] [review] v1 patch firstname.lastname@example.org
Attachment #92775 - Flags: superreview+
The use of "Warning" sounds dire, but I gather it's appropriate (as opposed to "Note" or "Important") if the user perceives data loss. We normally reserve "Warning" to matters of data loss or system corruption. The wording it too lengthy. Suggested rewrite (note capitalization change, too): "WARNING: Pipelining may improve page-load performance but is not fully supported by some web and proxy servers. This feature is for advanced users only."
Comment on attachment 92775 [details] [diff] [review] v1 patch r=gagan
Attachment #92775 - Flags: review+
what message are we going with here, the one Steve suggests, or somehting else? pls advise ...
I defer to Steve's expertise here.
yeah, the new wording (in comment #3) sounds better to me as well. new patch forthcoming...
Created attachment 92828 [details] [diff] [review] v2 patch reworded per Steve's suggestion.
Attachment #92775 - Attachment is obsolete: true
Whiteboard: [adt2 RTM] → [adt2 RTM] [ETA 07/27]
Adding adt1.0.1+ on behalf of the adt for checkin to the 1.0 branch. Please get drivers approval before checking in. When you check this into the branch, please change the mozilla1.0.1+ keyword to fixed1.0.1
Keywords: adt1.0.1 → adt1.0.1+
Pipelining is an HTTP feature -> qa to Tom. Should we just move the bug to HTTP as well?
QA Contact: benc → tever
Comment on attachment 92828 [details] [diff] [review] v2 patch forwarding r=gagan, sr=rpotts
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Keywords: mozilla1.0.1+ → fixed1.0.1
Resolution: --- → FIXED
verified 8/13/02 builds - winNT4, linux rh6, mac osX needs tested on trunk yet
Shouldn't this be reopened as it was never fixed on the trunk?
no, because this shouldn't be on the trunk (pipelining works ...)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.