[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnats/119: Major bug in textfields
From: |
magnust |
Subject: |
gnats/119: Major bug in textfields |
Date: |
26 Oct 2000 11:04:19 -0000 |
>Number: 119
>Category: gnats
>Synopsis: Major bug in textfields
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Oct 26 04:14:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: address@hidden
>Release: 3.113
>Organization:
>Environment:
>Description:
When typing '>>' in the beginning of a line, Gnats parses
this as a new field. E.g '>> text.....' after a newline
character would 'disappear' from its original location,
unpredictable behaviour so to speak. Seems like the 'new'
fields are put in the 'unformatted' section.
When you submit a report, the info in the textfields are
parsed with the sub unparsepr. The result from this sub would
look like this:
'>Number: xxx
>Category: xxx' etc...
If anyting inside a textfield happens to look like this,
Gnats will try to parse this as a new field.
And unfortunately, most email replies would have the
characters '>>' at the beginning of each line.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- gnats/119: Major bug in textfields,
magnust <=