This addresses the issue that some Caja HTML parser clients want to
render content without fixup including content with mismatched
escaping text spans.
The actual implementation of the fixup scheme is in the testcase but
if that looks good overall, it can probably move out of tests into
src.
Submitted @4504
http://codereview.appspot.com/4591043/diff/3001/tests/com/google/caja/parser/html/NodesTest.java File tests/com/google/caja/parser/html/NodesTest.java (right): http://codereview.appspot.com/4591043/diff/3001/tests/com/google/caja/parser/html/NodesTest.java#newcode657 tests/com/google/caja/parser/html/NodesTest.java:657: RenderContext renderContext = new ScriptFixupRenderContext(cat) If I set withAsciiOnly ...
15 years, 5 months ago
(2011-06-09 10:50:50 UTC)
#2
While this patch is fine as it stands, as discussed with Mike offline, this change ...
15 years, 4 months ago
(2011-06-14 03:43:23 UTC)
#6
While this patch is fine as it stands, as discussed with Mike offline, this
change is in the TCB and would be safer if RenderContext controlled whether
fixup will be applied or not (as in the first patch set) rather than applying it
unconditionally.
On Tue, Jun 14, 2011 at 9:13 AM, <jasvir@gmail.com> wrote: > While this patch is ...
15 years, 4 months ago
(2011-06-14 04:01:31 UTC)
#7
On Tue, Jun 14, 2011 at 9:13 AM, <jasvir@gmail.com> wrote:
> While this patch is fine as it stands, as discussed with Mike offline,
> this change is in the TCB and would be safer if RenderContext controlled
> whether fixup will be applied or not (as in the first patch set) rather
> than applying it unconditionally.
>
> http://codereview.appspot.com/4591043/
Applying this conditionally sounds fine. The first patch set had a
different problem that the way the ScriptFixupRenderContext was
defined and used was not going to go well with the
VanillaCajaHtmlSerializer code that I had pointed out to you - if you
could fix that (basically modify the first patch set so that the
comment/test mentioned in
http://codereview.appspot.com/4591043/diff/3001/tests/com/google/caja/parser/...
is addressed), that should be an acceptable solution?
Thanks,
Anupama.
Issue 4591043: Adds a release valve for CDATA content checks.
(Closed)
Created 15 years, 5 months ago by MikeSamuel
Modified 15 years, 4 months ago
Reviewers: Jasvir, anupama.dutta
Base URL: http://google-caja.googlecode.com/svn/trunk/
Comments: 3