From: Chris T. <ct...@sl...> - 2014-01-08 20:01:33
|
I suggest that you create a test project and experiment (which we can remove for you once you’re done). To our knowledge, the biggest item that doesn’t work with JS off is the “reply” button to make an in-line comment response. Currently, users will need to instead scroll to the bottom to add their comment to the bottom of the comment section. We suspect there are other cases of diminished functionality with JS off, however we believe them to be infrequently used, especially since they’re most likely Admin-only controls, which wouldn’t affect regular users or developers. -- Chris Tsai SourceForge.net Support sfn...@sl... ctsai-sf on irc://chat.freenode.net On Wednesday, January 1, 2014 at 11:53 AM, Fabian Keil wrote: > Christopher Tsai <ct...@sl... (mailto:ct...@sl...)> wrote: > > > We've recently pushed some changes that gets core functionality working > > even with js off. We can't do this for *everything*, but core functionality > > like posting tickets, login/logout, etc. should all be functional now. Does > > this satisfy your blocker for upgrades? Please take a look and let us know > > what you think. > > > > > Is there a list of stuff that is expected to break after the "upgrade" > or a complete list of "core functionality" that is assumed to continue > to work? > > Without this information we can't really decide whether or not we > could live with the "upgrade". > > Fabian |