Henning Koch

You're welcome :)

> I don't think that would work for me since what I'm trying to do is get away from a single point that knows about all compilers If there is...

> I work on large enterprise applications. Looking at ways of modernising legacy javascript on applications which can easily have 300-400 separate forms which have "behaviour" associated with them -...

A different approach to handle this was proposed in [RFC: Reconciliation of `` elements](https://github.com/unpoly/unpoly/discussions/446)

We're running a larger gem server using Geminabox. Having the compact index endpoint would speed up Bundler runs considerably. Hoping this can be merged!

> Also we would need to keep using DOMParser if we see a body or html element in the HTML. template elements can only parse fragments, not entire documents. This...

Preserving of playback state in media elements was recently revised 5dae584b08fae36f1c90c5103efb9fa9332a56f7. Unfortunately we cannot preserve media elements that are direct children of `` without lots of extra code, so we...

I'm going with *intended behavior* here.

Providing details about a partial match is not trivial, as Unpoly will usually attempt multiple fallback targets in multiple layers. We used to log about every attempt, which flooded the...

The use cases described in this issue should now be possible. See docs: - [Loading new assets](https://unpoly.com/handling-asset-changes#loading-new-assets) - [Registering compilers after booting](https://unpoly.com/up.compiler#registering-compilers-after-booting)