Suggestion: use cookie or localStorage for further pages on the same domain.

[FrankConijn]

By doing that, it is avoided that the Does-this-browser-support-the-needed-CSS-hyphenation? test script runs on every page of that particular website. Which, if I'm not mistaking, takes considerably more time than a cookie retrieval script.

[mnater]

Good point

[mnater]

Added with commit b101ac0

Todo:

• add documentation

[mnater]

Documentation: https://github.com/mnater/Hyphenopoly/wiki/cacheFeatureTests

[FrankConijn]

Cool, but for the sake of user-friendliness — beginner web designers will want to use your system, too — I would activate the cacheFeatureTests default. The cookie regulations do not concern cookies that only serve the user experience. And people really don't have any objections against those cookies. At least you should make clear where that Javascript line is to be found & altered, or pasted.

[FrankConijn]

Maybe you missed the last sentence of my last post, but I don't know where to change or paste this:

const Hyphenopoly = {
require: {...},
cacheFeatureTests: true
}

I cannot find it in either Hyphenopoly.js or Hyphenolpoly_Loader.js.

[mnater]

No, I didn't miss it. I just hadn't time to reply.

About activating the storage by default:
I'm not a lawyer and it's not only about the regulations in the EU. It's just safer if it's not activated.

Where to activate:
You don't need to change a line of code in Hyphenopoly.js nor Hyphenolpoly_Loader.js.
Hyphenopoly is the global object where you config how the scripts behave. See: https://github.com/mnater/Hyphenopoly/wiki/Global-Hyphenopoly-Object.
I updated the doc accordingly.