bugGNUstep Application Project - Bugs: bug #61921, [Grr.app] parsing of <PRE>...

 
 

bug #61921: [Grr.app] parsing of <PRE> is too crude

Submitter:  Riccardo Mottola <rmottola>
Submitted:  Tue 25 Jan 2022 10:09:04 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 25 Jan 2022 10:09:04 PM UTC, comment #1: 

This item has been reassigned from the project GNUstep Application Project support tracker to your tracker.

The original report is still available at support #110598

Following are the information included in the original report:

[field #0]                  Item ID: 110598

[field #1]                 Group ID: 1184

[field #2]              Open/Closed: Open

[field #3]                 Severity: 3 - Normal

[field #4]                  Privacy: Public

[field #8]                         : Unknown support Field Display Type

[field #9]                 Category: None

[field #10]             Submitted by: rmottola

[field #11]              Assigned to: None

[field #12]             Submitted on: Tue 25 Jan 2022 10:07:27 PM UTC

[field #13]                  Summary: [Grr.app] parsing of

 is too crude

[field #14]      Original Submission: Current implementation ignores any tag inside PRE.
However specification still mandates that entities should be escaped inside PRE.

A, hr, br, tt, code etc are permitted inside.
Yet newline and spaces and formatting are preserved. A little bit more complicated. Perhaps a "pre" status should be inside the parser, recurse but do not chew newlines/spaces when inside PRE..

[field #16]               Item Group: None

[field #17]                   Status: None

[field #18]        Component Version: None

[field #19]         Operating System: None

[field #20]          Reproducibility: None

[field #21]               Size (loc): None

[field #22]            Fixed Release: None

[field #23]          Planned Release: None

[field #24]                   Effort: 0.00

[field #28]                 Priority: 5 - Normal

[field #31]         Percent Complete: 0%

[field #33]                  Release: None

[field #58]     Custom Select Box #1: None

[field #59]     Custom Select Box #2: None

[field #60]     Custom Select Box #3: None

[field #61]     Custom Select Box #4: None

[field #62]     Custom Select Box #5: None

[field #63]     Custom Select Box #6: None

[field #64]     Custom Select Box #7: None

[field #65]     Custom Select Box #8: None

[field #66]     Custom Select Box #9: None

[field #67]    Custom Select Box #10: None


Riccardo Mottola <rmottola>
Group administrator
Tue 25 Jan 2022 10:09:04 PM UTC, original submission:  

Current implementation ignores any tag inside PRE.
However specification still mandates that entities should be escaped inside PRE.

A, hr, br, tt, code etc are permitted inside.
Yet newline and spaces and formatting are preserved. A little bit more complicated. Perhaps a "pre" status should be inside the parser, recurse but do not chew newlines/spaces when inside PRE..

Riccardo Mottola <rmottola>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rmottola (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-01-25 rmottola Reassign itemGNUstep Application Project, sr #110598 GNUstep Application Project, bug #61921

    Back to the top

    Powered by Savane 3.14-3b9d.
    Corresponding source code