You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lens templates with tables will potentially run into rendering problems if there are line breaks in the template. Part of the deeper jQuery 1.10.2/2.0.3 code (manipulationTarget) looks for children of a node when adding children to a table element to work with IE8, but if it's a TextNode, there will obviously be no children. The simplest author fix is to make sure <table><tbody> and </tbody></table> are used in lens templates without line breaks; a better fix might involve catching the problem before handing it to jQuery.
The text was updated successfully, but these errors were encountered:
I've posted a bug on jquery core: http://bugs.jquery.com/ticket/14290
The problem isn't only with newlines; as discussed there even whitespace
can break lens templates.
On 8/22/2013 4:09 PM, Ryan Lee wrote:
Lens templates with tables will potentially run into rendering
problems if there are line breaks in the template. Part of the deeper
jQuery 1.10.2/2.0.3 code (|manipulationTarget|) looks for children of
a node when adding children to a table element to work with IE8, but
if it's a TextNode, there will obviously be no children. The simplest
author fix is to make sure |
| and |
| are
used in lens templates without line breaks; a better fix might involve
catching the problem before handing it to jQuery.
—
Reply to this email directly or view it on GitHub #110.
Lens templates with tables will potentially run into rendering problems if there are line breaks in the template. Part of the deeper jQuery 1.10.2/2.0.3 code (
manipulationTarget
) looks for children of a node when adding children to a table element to work with IE8, but if it's a TextNode, there will obviously be no children. The simplest author fix is to make sure<table><tbody>
and</tbody></table>
are used in lens templates without line breaks; a better fix might involve catching the problem before handing it to jQuery.The text was updated successfully, but these errors were encountered: