Ondřej Žára

+1 for this. My music database uses `Cover.*` (capitalized), which is obviously not working with the current implementation.

Hi @ktiedt, it has been some time I wrote these, so my code knowledge is far from perfect. The `_hexSize` is the side size, yes. `_spacingX` and `_spacingY` are variables...

I might have omitted the fact that rot.js uses the "3: Double width" indexing approach mentioned in [the interactive manual](http://ondras.github.io/rot.js/manual/#hex/indexing).

So, the first image: - `width=4` - according to `compute`, `this._context.canvas[xprop] = Math.ceil( (options.width + 1) * this._spacingX )`, so the _main axis_ shall be 5 units (2.5 hexes) -...

Hi @nluqo, good finding! Thanks for the report. > * The only valid input seems to be positive numbers. Right, the `number` type is also mentioned in the autogenerated documentation:...

> I'd put (pre-salt + the string + post-salt) through SHA-256 and then pull the least significant bytes to turn into a seed value. The RNG uses four state values,...

> https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest Also, I would prefer the seeding process to be synchronous :-)

Sounds a bit like an overkill to me. We just need a way to convert a string to three 64bit values, without any particular crypto/security properties... how about the original...

How does this relate to line breaking? I suppose that contextually-replaced characters only apply to the case when two (or more?) related glyphs are not broken-within, right?

Pretty neat :) Please note that the `registerElement` API is deprecated and browsers are implementing the **V1** API, `window.customElements.define()`. This proof of concept for the homepage is merely a showcase...