Nico Hoffmann ෴.
Nico Hoffmann ෴.
Fair point. I wasn't trying to argue for relying on a fast safe - it should work for fast and slow scenarios. I was just surprised to hear that it...
But editors would not even know that on disk it is `The quick brown fox@` and they could back to this clicking Revert. They would think clicking revert gets them...
Honestly this sounds like quite the headache to implement - any additional store has proven always to be quite the nightmare to handle. I know some might hate this, but...
Yes, but it also has a reason why this hasn't been touch for more than 2 years: it's a lot of pain, a lot of edge cases, a lot of...
What we could do is - Use `k-textarea-input` instead of `k-writer` for the block preview whenever the drawer's `text` field isn't of type `writer` - Add a new "plaintext only"...
@lukasbestle could you say a few words on why we can't fake the timeout? Would be curious to understand
Hard to say for me in regards to performance. Another half-fix could be that we allow force-storing values via `::create()` or `::update()` that the system thinks don't (yet) exist.
We have started refactoring our blueprint and form classes. Would be best to tackle this, once that's done.
Looking at this, I think it actually shouldn't be the section which defines whether pages are sortable or not. But the blueprint of the page itself.
@lukasbestle but don't we have that situation already if e.g. blueprint A has `num: date` while blueprint B has `num: default`?