Skip Menu |

This queue is for tickets about the DBIx-XHTML_Table CPAN distribution.

Report information
The Basics
Id: 21761
Status: resolved
Priority: 0/
Queue: DBIx-XHTML_Table

People
Owner: JEFFA [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.36
Fixed in: 1.38



Subject: Special XML characters should be expressed as entities
If some database cells contain some special XML characters like "<", then the resulting XHTML could be invalid. It would be nice if DBIx::XHTML_Table would make entities of these special characters *by default*. For now, one can use something like $table->map_cell(sub { html(shift) }) to do it manually, where html() is some escaping function. For some obscure applications where database cells already contain valid XHTML snippets there could be an option to not do auto-escaping. Regards, Slaven
Will be ready in V1.38
Note that starting with v1.45 you will have to request HTML encoding explicitly: $table->{encode_cells} = 1; I had forgotten that HTML encoding was unfavorable because i like to put HTML text boxes inside the table cells. This bug fix broke that feature, so hopefully v1.45 will provide a good compromise. On Thu Sep 28 10:18:47 2006, SREZIC wrote: Show quoted text
> If some database cells contain some special XML characters like "<", > then the resulting XHTML could be invalid. It would be nice if > DBIx::XHTML_Table would make entities of these special characters *by > default*. For now, one can use something like > > $table->map_cell(sub { html(shift) }) > > to do it manually, where html() is some escaping function. > > For some obscure applications where database cells already contain valid > XHTML snippets there could be an option to not do auto-escaping. > > Regards, > Slaven >