creating InlineEditBox using 'first' position doesn't hide original text properly

[guest]

If you create an InlineEditBox? using the additional position argument to createWidget will cause the following erroneous behavior. When the text is clicked on, the widget appears and behaves properly, except that the original text is displayed immediately after widget.

Looking at the generated HTML, you can see that it creates the widget _and_ the span with display:none with the original text. That's good. But immediately after that is the original text again...

Attached code demonstrates.

[guest]

One correction to bug report: when the widget first appears (not just when clicked on0 it is inserted before the original text, rather than replacing it. The expected behavior is that the original text should be replaced by the clickable widget...

for further bug report info please contact: jeffg@…

[alex]

if you want the widget to replace the node in question, just drop the placement argument. It's functioning as expected.

[guest]

No you have it wrong (I think). I need to use "first" and it doesn't work as shown by the code I attached. I don't want to replace the node... I need to use "first" so that the position of the InlineEditBox? is correct (remains in the same place), because if I don't use "first" then the element moves somewhere else (below element that contains the element I'm supplanting with the inlineEditBox. I did not show that in the code I supplied, but if you have a large element with a subelement positioned within it (absolute coords), and then create an inlineEditBox with the default arguments, as you suggest, you will see that the inlineEditBox appears below.

Not that all the tests for inlineEditBox do not try this!

And using "first" definitely does _NOT_ work as my code shows? You did try it right and it definitely doesn't work correctly.

jeffrey / jeffg@…

[guest]

correction: The line reading: "Not that all the..." is garbled. It should start with: "Note:" rather than "Not"

Currently no test in dojo tests the inlineEditBox as I describe above... validating where an inlineEditBox appears when supplanting a precisely positioned child node within another larger (parent) element. It does not seem to work properly for me. I can supply a test case if you need me to.

[bill]

createWidget() itself is no longer supported, so we won't fix this bug.

[(none)]

Milestone 0.4.4 deleted