Hussein Shafie schrieb:
I cannot reproduce the problem you describe using our simple test case
(see attached forced_deletion.xml and forced_deletion.css. [...]
The stack trace below seems to show that the bug is triggered by a
specific use of the label() CSS extension. See
http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/label.html
Please be kind enough to tell us how to reproduce this bug. You can
either modify the simple test case I've attached to this email or send
us a document and a CSS of your own.
Thank you very much for your valuable hints! You are of course absolutely right
that the undesirable behaviour I encountered is related to my usage of label().
Sorry for not having checked my CSS in the first place.
See the attached version of the CSS test file you kindly provided, in which I
added the same type of XPath expression I have used in my configuration. That
label() statement which tries to access a replaced node reliably reproduces the
bug.
It is a bit inconvenient that the (only?) workaround I found seems to imply
manual refreshing, but at least XXE's document pane keeps being usable that way.
Yves
book,
part,
head,
tail,
body {
display: block;
margin: 0.5ex;
}
book
{
display: block;
collapsible: yes;
collapsed: no;
not-collapsible-head: 0;
/* this would refresh automatically, but makes XXE loose keyboard focus;
probably because the XPath target node is temporarily unavailable
*/
collapsed-content: collapser() " " label(xpath, "part[1]/*[1]");
/* this might do as a workaround, but requires manual refreshing
collapsed-content: collapser() " " xpath("part[1]/*[1]");
*/
}
book:before
{
content: collapser();
}
part {
border: 2 solid gray;
padding: 0.5ex;
}
body {
background-color: #E0E0FF;
}
tail {
background-color: #E0FFE0;
}
head {
background-color: #FFE0E0;
}
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
