Inline Edit Suggestions

Antranig Basman antranig at
Wed Dec 10 16:05:46 UTC 2008

Hi there Everett - thanks for your investigations. On the first point,
there seems to be a deeper problem, since we are indeed hiding the
edit control with display:none and not visible:hidden - the latter which
I don't think even has any visible effect - in the example you have
put up, only the 3rd field, that which is marked with display:none,
is not shown visibly.
This is almost certainly some form of bug in JAWS - since the edit
field is correctly hidden on startup, but not after it has once been
shown, even if it is returned to the same CSS condition. But the
question is how we can effectively work around this problem - 
I can think of only two things to try
i) mark the input field itself, as well as its containing <span>,
with display:none, or
ii) when it is "hidden", physically remove it from the document rather
than just hiding it.

ii) promises to be perhaps more effective, but also more problematic,
since the effect of removing some more complex editable control such
as an FCKEditor will very likey be destructive.


E.J. Zufelt wrote:
> Good morning,
> After having tested the inline edit example (
> )
> with JAWS 10, I have the following feedback.
> 1. After I press enter to submit changes to the editable text the edit
> control remains visible to JAWS.  It was mentioned on irc yesterday that
> this could be because the edit control is being hidden with visible:hidden.
> I have tested this and it is correct.  The edit control needs to be hidden
> with display:none.
> I have made an example to demonstrate at (
> ).  JAWS detects the first
> two edit controls on my example page, but not the third.

More information about the fluid-work mailing list