public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: sherry.wasserman@comverse-in.com To: gnats-gnats@sourceware.cygnus.com Subject: gnats/171: Text field paragrahps are lost during edit if they are too long. Date: Mon, 02 Apr 2001 11:14:00 -0000 [thread overview] Message-ID: <20010402180925.30225.qmail@sourceware.cygnus.com> (raw) >Number: 171 >Category: gnats >Synopsis: Text field paragrahps are lost during edit if they are too long. >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Apr 02 11:14:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Sherry Wasserman >Release: gnatsweb 2.6 >Organization: >Environment: gnats 3.113 on UNIX_SV 4.2MP 2.1.3. Note: Gnatsweb and gnats run on the same machine. >Description: A text field paragraph containing more that 512 characters will disappear when the submit-edit is pressed in gnatsweb. A paragraph of 512 or greater will survive when the PR is created; but when the PR is edited it will disappear, even if the text field with the long paragraph is not changed. When text is added to a paragraph that is originally shorter than 512, the whole paragraph disappears if the resultant size is 512 or greater. This happens in Description, How-To Fields, and Fix fields. (This is similar to the recently closed PR27, but slightly different.) >How-To-Repeat: 1. Create a PR with a description of more than 512 characters without any carrage returns. 2. Edit the Pr, but don't change the original description. 3. View the PR - the description is gone! >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-04-02 11:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010402180925.30225.qmail@sourceware.cygnus.com \ --to=sherry.wasserman@comverse-in.com \ --cc=gnats-gnats@sourceware.cygnus.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).