#1292: Issues with the FPF and HTML5 elements.
-----------------------------------------+----------------------------------
Reporter: jeanphilippe.d...@… | Owner: david
Type: defect | Status: assigned
Priority: normal | Milestone: 1.0.4
Component: filter | Version: 1.0.3
Severity: normal | Keywords: html5
Has_patch: 0 |
-----------------------------------------+----------------------------------
Changes (by david):
* status: new => assigned
* component: _OTHER_ => filter
Comment:
The problem here is libxml which throws the error when using HTML parsing
mode. We cannot fix this directly. As an immediate workaround, you have
two options:
1. Force XML parsing mode
1. Instruct FPF to ignore parse errors (but then it won't re-populate the
form)
The first option is probably doable for you (I can't see why it wouldn't
be). The second one is of course not very satisfying.
I think it would be a good idea to make FPF more lenient with parse errors
in HTML parsing mode. The problem in this particular case is that the
unknown tag is treated as an error by libxml, not as a warning. We can
work around that by treating this particular error code (801) as a warning
instead. We could then ignore at least all warnings, and possibly even
errors, since they are non-fatal in HTML parsing mode (but fatal in XML
parsing mode). I opened a separate ticket for this general area of work,
#1307.
--
Ticket URL: <http://trac.agavi.org/ticket/1292#comment:1>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
