This is not working correctly.    I have settings as follows and they are not freezing columns and rows in both view and edit mode.  Please fix. Creating large tables are USELESS without this feature..

+1

Why can't this simple fix be implemented?

how i solve this problem i made a table in confluence template i want to set the width of cell. How i set the width of row cell forecast that dnt increase if i add something in project team and stakeholders cell

After testing on Confluence Server 7.4.13, I noticed that the header freeze functionality is disabled the moment I add a page property report somewhere in the table.

Could it be possible that the macro is actually generating another table within the table thus disabling the freezing functionality?

Still doesn't work. I ll just use Excel. They solved this about 20 years ago

After testing this for a couple of hours, it looks like it works ok with Confluence 7.4.0 (at least for simple tables). With a few mentions:

1. it doesn't seem to work with old tables. So if you have old tables where you'd like to use this feature, you might need to extract the data from them and add it to a new table.
2. it doesn't work in Edit or Preview modes (not sure why). You need to Save changes. So if you wanna experiment with this feature, my suggestion would be to create a test page.
3. doesn't work anymore if your table contains merged cells. Interestingly enough, Google Docs' "freeze row" feature works just fine with the exact same table. So...maybe we can have that, too? That would be awesome. Or maybe there's a workaround for that and I haven't found it yet.

Suggestion: if it's not supposed to work with merged cells (though, again, Google seems to have done it somehow), please, implement a warning/notification, something to let the user know that if he's gonna merge cells, this functionality will be disabled.

Anyway, I hope this comment helps other people. It was definitely frustrating for me not to have it working for so long.

Looking at the creation date 3 years from now this won’t be fixed any time. Just give them your money for the cloud and f*k off. They don’t give a s*t if some smaller functions that are not implemented correctly are not working for a handful of people. 

The workaround mentioned above doesn't work for me. Is there any news on this?

+1