Thought I'd post this here before going the support route.
We have java code that handles the DOMNodeInserted event to strip out Pub LcL pseudo-attributes from nodes when they are inserted, either by copy/paste or a move. This has worked fine till we ran into an issue when users decided to create new columns in a table.
It seems that when a column is inserted, a DOMNodeInserted event is fired for each <entry> node that is put in, however, no attributes are found when either querying via the ACL oid_has_attr or by looping over the AElement getInternalAttributes() results. Doing either of these on a non-table node returns the expected attributes.
Now, this would make sense since the entry should be "new" and therefor have no attributes associated with it. The funny thing is, after the insert, pseudo-attributes do show up in the source that are identical to the ones present on the original column.
Right clicking on the first column, and selecting Insert->Column Left produces the following:
<table>
<tgroup cols="3">
<tbody>
<row>
<entry></entry>
<entry>Col1Value</entry>
<entry>Col2Value</entry>
</row>
</tbody>
</tgroup>
</table> Notice that while the entry is "blank", the hidden attribute still shows up with the same value as the "reference" column.
Has anyone run into this before?
I found some ACL that handles this using the tbl_obj_add_after and tbl_rectangle_copy_after callbacks, but shouldn't this work with DOMNodeInserted as well?
