Before reporting a bug, please read these guidelines, and make sure you provide the maximum amount of information that you can.
We only support the latest version of firefox for development of the beta series. Later, when we go to production, we will support Safari, and possibly other browsers, as requested. The first thing to check is if the problem is visible with the latest firefox version or not.
If you suspect a bug in the algorithm used in one of the data-modules, you can take a snapshot of the JSON data-structure to include in the bug-report. Simply right-click on the content-area of the module and select 'Show table/treeview data (JSON)'. This will create a pop-up window which contains the data. Cut-and-paste this into your bug-report.
If you can get a screen-shot, please do. Especially if your report concerns the visual layout of information.
Spend some time trying to understand if the problem is reproducible. Non-reproducible errors are extremely hard to debug, obviously! Does it happen only if you navigate a certain path (load page, select module, set filter?) or does it happen if you save a bookmark to the current page and reload it?
Does the problem apply to all modules of the same type (all treeviews or all datatables?)? Does it depend on the sorting or filtering options?
We may need to check server-logs to see if that contributed to your problem
The next-gen webapp uses the browser history to maintain a significant amount of state-information about the page you are viewing (the module, its arguments, and any sort and filter options you have set). You can cut-and-paste the URL from either the browser address-bar or from the Link button on the page to get the current page-state. Include this in your report.
Check to see if someone else has reported the same problem before reporting it yourself. If it has been reported already, see if you can add anything to the ticket that might help in the diagnosis
Once you've got all that information, go ahead and report this bug