Does not work in View

In order to sidestep this problem I tried using the Insert Block Module. The results were exactly the same as for Viewfield.

Well now it is not at all clear that this issue is related to Viewfield. I experience the same problem with a block in normal block region and also in a page view.
The view is of user profiles with editable content fields.
As I mentioned above the view was working fine until 5 March at which point I did two things.
1. Updated Drupal core to 6.16 (following this update Insert View was condemned as evil and Viewfield was reconmended in its place)
2. Installed Viewfield (to which I attributed this problem, probably too hastily)

I have also suddenly experienced problems with Views Bulk Operations on the same set of editable fields. I have uninstalled Insert View (obviously), Viewfield, Insert Block and VBO but the problem still exists with editable fields in a page or any other view.

Perhaps the problem is Drupal 6.16 inconjunction with Ajax Load or Jquery update.

Any clues would be appreciated.

Changed title from "Does not work in viewfield" to "Does not work in View"

I have checked my Drupal 6.16 update with a rules based comparison of all files on the server. I have deleted the data, data fields, content type and views. I have cleared all caches. I have reconstructed the whole scenario from the ground up, created a few nodes, populated some data fields and recreated a page view. The view is a content profile as before with click to edit fields.

The symptoms are still there except that a javascript error is not reported. This may be because I am now dealing with only six nodes not 200 plus. When the page first loads the [Edit] shows up in the editable fields but progressively disappears field by field in a few seconds. If [Edit] is clicked while it is visible the field can be successfully edited. Once it has disappeared it is not accessible.

Is anyone else experiencing this problem?

Can anyone help?

This is obviously related to #699954 and #703988

In addition, my experience is:
1. Javascript errors are reported when there is a large number of nodes in a View as [Edit] is progressively faded.
2. Cannot edit multiline text views at all: cursor cannot enter the text area.
To elaborate on this second point:
If the field is empty it cannot be edited. If it has data in it, the text area opens but any attempt to place the cursor in the field closes the field. If editablefields.js is modified as Undoit proposes in his first comment on #699954 then empty fields can be opened and edited. Including multiline text fields. However once it has data in it it can't be changed within the view.

These bugs make the module unusable for me and so I am upgrading the priority to critical.

This is an extraordinarily useful module and my hearty congratulations to the developers. However, this sure needs to be fixed.

Thanks.
Unfortunately I am very much an amateur and I can't suggest a patch in what, to my little mind, is a complex script with big changes from 6.x-1.2.
Apart from the problem with multiline text areas I can achieve my requirements by disabling the fading out of [Edit] as per #699954: Disable Hiding of Click to Edit So I have done that to get by to some extent.

Addressing the multiline text area using Firebug there are three cases:
1. The field is empty.
Click on [Edit].
Click in the text area.
Cursor appears.
Type entry.
Click outside the text area.
Data POSTed and text area closes.
Good!
2. Field is not empty.
Click on [Edit].
Click in text area.
POST is called prematurely.
Text area closes.
Unable to edit.
Not good.
3. Field is not empty.
Can't see cursor but assume it is there and use Ctrl A to select text.
Text appears selected within the text area. (Although using Ctrl X has no effect.)
Delete selected text using Del key.
Text disappears.
Click in text area.
Cursor appears.
Edit text area.
(Other key stroke sequences may make the text area editable but I haven't found any yet. In most cases as soon as the cursor is clicked in the text area POST is called prematurely and the text area closes without changing the field contents.)
Click outside the text area. (Or try anything else.)
POST cannot be called.
Text area remains open until page refreshed.
Data not edited.
Not good.

Mark. As I noted in #699954: Disable Hiding of Click to Edit , your fix solved the editing of empty fields, the javascript errors and the client CPU load. Fixed for 200 nodes in a view all empty and all full. Great!!!

However, I still have the problem that I can't edit multi-line text areas as I have described above.

Single line text fields and select from a list work fine.

Having stared endlessly at the javascript (not having too many other tools at my disposal) I can only deduce that, like check boxes, multi-line text fields need a special case to ensure that focus, blur and post methods are reliably called. As an example the current approach of click outside the text area to call post is potentially unreliable, I suspect. If focus is not effected when the text area is opened, clicking in the text area will do exactly what I described, ie, call post prematurely.

Well, I was about to say that I have experienced this in this Firefox, IE8, Chrome and Opera. However, just to be sure, I went back and tested each browser in turn trying to edit a field with data in it. Chrome, and to my surprise, IE8 and Opera all worked OK, ie, edited the fields correctly. In Firefox, my default browser, the problem recurred as I described, ie I couldn't enter the text box to edit. I had previously emptied all server and browser caches and, in the case of FF done a complete restart. And prior to that I had reconstructed everything from the ground up including deleting views and content fields and types, deactivating and uninstalling all the concerned modules and reinstalling them. Then I recreated the content types, cck fields, views and reimported the data.
So, in summary, the problem remains in FF, but nowhere else. There is obviously something wrong with what I am doing, but surely only one small step from resolving it.

I was using FF3.5 and everything I described occurred with that version.
However, after your question I checked for updates and installed 3.6.
I then tested again using FF and Chrome.
This time something different but the same behaviour in each browser.
In FF3.6 I am now able to edit both an empty and a occupied multi-line text field. Clicking in the text box immediately puts the cursor in place, I can change the contents and save by clicking outside the box. "Wow", I thought. The same in Chrome.
I then tried to edit a field but leave it unchanged. Whether it had contents or none. In both FF and Chrome I can't leave a field unchanged. Clicking outside the box does not close the box.
This doesn't seem to me to be ideal but it is bearable. By refreshing the browser the boxes close and the data remains the same.
I haven't the faintest idea why the change from FF3.5 to 3.6. I have repeatedly cleared the browser cache and closed and reopened it and rebooted my pc but I haven't experienced changes in behaviour like this.
On the web site, the theme I am using is Roople Tapestry. I can't see any css styles inherited by the surrounding elements from the theme which could make any difference. I might not be looking in the right places of course.
Thanks for your patience in helping me get through this.
Regards, Graham

In fact you make this point yourself in #11 above: it is an on change event not an unfocus. I can live with that.

I really appreciate the help and effort. Thanks, Mark.