michael-e

I would not vote for this additional feature, simply because `srcset` is not in the original Markdown specs. (However, I admit that I always post-process HTML with XSLT, so I...

@lewiswharf: There is another issue with your apprach. In the case of post save filters, it might be that your event returns success but the filter fails. In this case...

> If I'm honest, I can't really remember why I normalize in the first place... I can't imagine any reason to do this in form-controls.

I chose an XSL variable because you can include XSL logic, if you like. :-) Of course you shouldn't do that. But theoretically...

I wouldn't oppose this solution either, but I prefer to rename the Symphony class. e.g. to `SymJSONException`. This, at least theoretically, allows custom error handling in Symphony.

OK, done. Please take a look and comment. All my systems are on PHP 7.3 now, so chances are that I will notice any hickups if they still occur. :-)

I remember a discussion (long time ago) about this, and a simple solution: Add an event to your page to manipulate the form data. Here is an example event: ```...

What exactly would it mean for a custom-coded event to be "filterable"?

So you talk about `pre-load` filters exclusively. (Section events have `pre-save`, `post-save` and `final-save` filters.) No, I am not against this idea! It increases flexibility.

And what about `post-execute`? :-)