Nico Hoffmann ෴.

Results 819 comments of Nico Hoffmann ෴.

That doesn't solve the dragging issue - I think the sortable library has an issue that it's not happy when dragging in visible overflow space.

> The upload should be disabled, as one would expect that updating a page also includes changing the files belonging to the page. I think this is rather a point...

I can see your point. The counterpoint is that there are specific files permissions. Could be weird as well when you think you've set them right but a very different...

I'd second @lukasbestle's suggestion. We can be annoyed by the general issue, but that's where Markdown syntax just collided with a variant of gender neutral script. Nothing really to do...

@bastianallgeier I tried with the paste rules from tiptap ```js pasteRules({ type, utils }) { return [ utils.markPasteRule(/(?:^|\s)((?:_)((?:[^_]+))(?:_))/g, type), utils.markPasteRule(/(?:^|\s)((?:\*)((?:[^*]+))(?:\*))/g, type) ]; } ``` However, if I try to paste...

> sizes defines a set of media conditions (e.g. screen widths) and indicates what image size would be best to choose, when certain media conditions are true — these are...

@lukasbestle this one would be ideal for a summary - it feels like you all were already quite close to a concept, but breaking the last state down would be...

# Summary The issue arises as the data shown here originates in `Panel\Model::pickerData()` where text gets escapes via `->toSafeString()`. While the preview bubble itself would be safe without escaping (as...

@jaro-io Could you elaborate a bit on how you would like to use query syntax in the structure field columns? Your example of `'{{ page.something }}'` doesn't make much sense...

That is from dynamic options (e.g. select field). But the columns in a structure field are exactly for the fields from the structure field. So you don't need any query...