Interesting module! What is the behavior when javascript is disabled or not supported? Do authenticated users receive uncustomized (anonymous) pages?

Comments

Janne Salo’s picture

Janne Salo commented

Unfortunately, the module doesn't degrade very gracefully if JS is disabled. Most likely you'll see the missing components loading forever (the anonymous content is on the page, but initially hidden).

jdleonard’s picture

jdleonard
he/him
Primary language English
Location Austin, Texas
commented
Title: Behavior when JS disabled? » Improve behavior when JS disabled
Category: support » feature

Then I'll turn this into a feature request :)

It would be fantastic if there was graceful degradation. Not sure what the best approach is though.

eme’s picture

eme commented

Shouldn't be possible (and let's hope easy) at least to disable the cache for authenticated people with no js ? There are not that many people with js desactivated and it may not be a too heavy performance hit.

Janne Salo’s picture

Janne Salo commented
Status: Active » Closed (won't fix)

It's probably not worth the trouble to work on graceful degradation. Or even possible, since the whole logic relies heavily on being able to run code client-side.

As to eme's question on authenticated people with no JS: currently the module doesn't support serving pages past the cache if no JS support is detected. I'm not sure how such feature could be implemented in a way that's not a messy kludgy hack. I guess it would require altering all, or at least most, of the links on the site.

In a nutshell, I'd advice against using Cache Control if you know significant proportion of your users won't be running JS.

If you have any objections and feel this is an important matter to you, feel free to send patches or suggestions (or just voice your concern), and we'll see if we can do anything about it. In the meantime, I don't consider this a priority.