server-side rendering support

[jamnanlaw]

Currently the code has some dependencies on the client-side DOM, e.g.

1. FixedDataTableColumnResizeHandle componentWillMount has dependency on document.body
2. getActiveElement (which in turn dependent on document.body) is used

Is there a plan to make this component support isomorphic application?

Thanks.

[pieterv]

@jamnanlaw I have a fix ready to sync which fixes the two issues you pointed out :) with this change the table renders from the server great, the problem we then have is that react cannot mount onto the rendered HTML since its renders differently based on the environment :(, this is the main culprit: https://github.com/facebook/fixed-data-table/blob/master/src/vendor_upstream/dom/translateDOMPositionXY.js#L23-L45. We will probably need to change the code to always render with top and left on the first pass then use translate if the browser supports after that.

So a long answer but yes we intend to support server rendering :)

[grahamb]

Has there been any update on this? Server rendering is working, but throwing warnings in the browser:

Warning: React attempted to reuse markup in a container but the checksum was invalid. 
This generally means that you are using server rendering and the markup generated on 
the server was not what the client was expecting. React injected new markup to compensate 
which works but you have lost many of the benefits of server rendering. Instead, figure out 
why the markup being generated is different on the client or server:
 (client) ight:50px;z-index:1;transform:translate3
 (server) ight:50px;z-index:1;left:0px;top:0px;" c

[ghost]

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

[AlesJiranek]

Is there any update on this? I have same problem as @grahamb

[pieterv]

Sorry no we haven't made any progress here, this just isn't a use case we have needed. The solution described above is still valid and shouldn't be too hard if someone wants to have a go at solving this.

[wcjordan]

@AlesJiranek @grahamb @jamnanlaw we've merged the PR for this into our fork at https://github.com/schrodinger/fixed-data-table-2 and should have the fix up on npm within a week.