Hi,

I'm trying to use my xml2rfc configuration, which includees the
following css, with xxe on MacOS 10.4.1 + java 1.4.2.  It worked as
expected in MacOS 10.3.9:

rfc::attribute() {
        attribute-content-left: "[" attribute-label() ":";
        attribute-content-middle: value-editor(attribute, attribute());
        attribute-content-right: "] ";
        font-size: 80%;
}

rfc:before {
        display: block;
        content: division(content(paragraph(content("RFC metadata: ",
attributes()))));
        padding: 2px 2px 0 2px;
}


(The content of rfc:before was more complex, but I simplified it to
make sure there wasn't some other interaction going on).

The DTD for the rfc element looks like:

<!ATTLIST rfc
          number      %NUMBER;           #IMPLIED
          obsoletes   %NUMBERS;          ""
          updates     %NUMBERS;          ""
          category    (std|bcp|info|exp|historic)
                                         "info"
          seriesNo    %NUMBER;           #IMPLIED
          ipr         (full2026|noDerivativeWorks2026|none
                      |full3667|noModification3667|noDerivatives3667
                      |full3978|noModification3978|noDerivatives3978)
                                         #IMPLIED
          iprExtract  IDREF              #IMPLIED
          docName     %ATEXT;            #IMPLIED
          xml:lang    %ATEXT;            "en">

When editing either the category or ipr attributes on xxe 2.9 or 2.10
on MacOS 10.4.1 with java 1.4.2, the inline popup box behaves
strangely: the first time you pick it, it pops up as though you could
pick an item in it and then instantly pops down again, leaving a
glowing blue "selected" border around the item but not allowing you to
change it.  If you click a second time, you're permitted to select a
new value as expected.

The attribute editor does not display this behavior - it allows
changing the value on the first click, as expected.

This is very likely an Apple bug, of course, but I don't know enough
of what xxe is doing to be able to report the bug myself.  I'm happy
to report it if you can help build a simple test case that shows off
the behavior difference between 10.3.9 and 10.4.1.

Thanks,
  Bill

Reply via email to