Thanks Jiri! That's what I wanted to know. I'll ask the admins at my company if we can upgrade to 6.14 to pick these up.

This bug was fixed as part of the editor upgrade in 6.14.

We are working through a large backlog of editor related tickets and confirming they are truly fixed.

That's why some of them still appear as unresolved. Sorry about delay!

Unfortunately, Atlassian development does not value communication with it's end-users as much as we would like.  Given that the status of this issue is still 'unresolved' and that the 'representative' is now displayed as 'inactive', I doubt there will be any feedback on the status of this issue.

It's been almost a year and Confluence 6.14 is out with editor improvements. Any chance this has been fixed?

Hi cmaynard2,
We have been in the process of doing a major upgrade to the editor which we use in Confluence. This involves upgrade the TinyMCE editor from version 3 to version 4. This is a large project which we started shipping the new editor for evaluation and Marketplace App compatibility in Confluence 6.8 (Preparing for Confluence 6.8). This activity has been ongoing in the upcoming Confluence 6.9 release. The actual project will ship in 6.10 or later depending on the feedback and issues that we may need to address before making available to customers. Part of upgrading the editor results in a whole range of bug fixes which we have not targeted through the usual process of prioritising a bug, assigning it, putting it into progress, marking it awaiting release and then releasing it.
It is because of this that you should expect to see a number of bugs make a faster transition from 'Open' to 'Awaiting release' to 'Fixed' as part of this larger project.

Can you provide us some feedback on what your definition of 'near future' represents in actual calendar date?

Can you also provide us some feedback on what the other changes are in the 'project we have to improve the editor' and dates related to those changes?

Just based upon the status of this issue it is still 'unassigned' so how can this issue be 'fixed in the near future' if no one is assigned?

My apologies on such skepticism, but the extensive number of issues that are still 'open' for an extended period of time only gives us doubts as to the possibility of this being 'fixed'.

Thank you! good news

Not being able to clear multiple cells in a table at one time is a time suck!  Often, we will copy and paste an existing table and then need to clear out most of the cell values.  Having to individually delete cell contents is time consuming and especially frustrating because, in my opinion, such a simple function is basic and should be apart of any company's table editing software.