Revision history [back]

click to hide/show revision 1
initial version

answered 2018-09-12 11:10:46 +0800

cor3000 gravatar image cor3000

ZK Team

Really weird and I don't have an explanation why this happens right now ... looks/feels like a zul parser bug. (native elements are handled a bit special since multiple native elements can compact into a single widget in the server response) e.g.: ['zk.Native','i5LQa',{prolog:'<tr> <td> ',epilog:' <\/td> <\/tr>'},{},[ ... children ...]

I'll post a bug shortly.

As a workaround you can add the condition directly to the node you want to show/hide without the <zk> element:

<n:tr if="${vm.visible}">
  <n:td>
    <label value="Should be visible, too" />
  </n:td>
</n:tr>

Your updated example using the workaround: http://zkfiddle.org/sample/3ikg0ch/6-Weird-bug-with-native-HTML-and-zk-if-workaround

Really weird Weird indeed and I don't have an explanation why this happens right now ... looks/feels like a zul parser bug. (native elements are handled a bit special since multiple native elements can compact into a single widget in the server response) e.g.: ['zk.Native','i5LQa',{prolog:'<tr> <td> ',epilog:' <\/td> <\/tr>'},{},[ ... children ...]

I'll post a bug shortly.

As a workaround you can add the condition directly to the node you want to show/hide without the <zk> element:

<n:tr if="${vm.visible}">
  <n:td>
    <label value="Should be visible, too" />
  </n:td>
</n:tr>

Your updated example using the workaround: http://zkfiddle.org/sample/3ikg0ch/6-Weird-bug-with-native-HTML-and-zk-if-workaround

UPDATE: I posted ZK-4055 with the above and an alternative workaround

Weird indeed and I don't have an explanation why this happens right now ... looks/feels like a zul parser bug. (native elements are handled a bit special since multiple native elements can compact into a single widget in the server response) e.g.: ['zk.Native','i5LQa',{prolog:'<tr> <td> ',epilog:' <\/td> <\/tr>'},{},[ ... children ...]

I'll post a bug shortly.

As a workaround you can add the condition directly to the node you want to show/hide without the <zk> element:

<n:tr if="${vm.visible}">
  <n:td>
    <label value="Should be visible, too" />
  </n:td>
</n:tr>

Your updated example using the workaround: http://zkfiddle.org/sample/3ikg0ch/6-Weird-bug-with-native-HTML-and-zk-if-workaround

UPDATE: I posted ZK-4055 with the above and an alternative workaround

version 8.6.0.FL.20180917 contains a fix which will be also contained in 8.6.0

Weird indeed and I don't have an explanation why this happens right now ... looks/feels like a zul parser bug. (native elements are handled a bit special since multiple native elements can compact into a single widget in the server response) e.g.: ['zk.Native','i5LQa',{prolog:'<tr> <td> ',epilog:' <\/td> <\/tr>'},{},[ ... children ...]

I'll post a bug shortly.

As a workaround you can add the condition directly to the node you want to show/hide without the <zk> element:

<n:tr if="${vm.visible}">
  <n:td>
    <label value="Should be visible, too" />
  </n:td>
</n:tr>

Your updated example using the workaround: http://zkfiddle.org/sample/3ikg0ch/6-Weird-bug-with-native-HTML-and-zk-if-workaround

UPDATE: I posted ZK-4055 with the above and an alternative workaround

version 8.6.0.FL.20180917 contains a fix which will be also contained included in 8.6.0

Support Options
  • Email Support
  • Training
  • Consulting
  • Outsourcing
Learn More