Can set 1/3 width field in 1/2 width column, but can't set 1/2 width field in 1/3 width column?

Kirby 3 Questions 🤔
1

I have a two column layout in the blueprint, 2/3 and 1/3 width respectively.

I want to put two fields side by side (1/2 width) within a 1/3 width column, but it looks like it has no effects.

When I set the column width to 1/2, it started to work.

However this restriction doesn’t make sense to me, since you’re allowed a 1/3 width field within a 1/2 width column, so in both cases you end up with a 1/6 width field (with respect to the whole page).

2

I just tried this myself, and yes, that doesn’t seem to be possible. You could try to change this with a custom Panel stylesheet, I guess.

3

Is this considered a bug? It’s not outright broken but it breaks expectation.

4

It’s probably like that on purpose, but doesn’t make much sense considering that you can go as small as 1/12 in a 1/1, 1/2 or 2/3 column, but any field width setting in a 1/3 column or smaller has no effect.

5

I found the offending CSS styles:

.k-sections>.k-column[data-width="1/3"] .k-fieldset .k-grid,
.k-sections>.k-column[data-width="1/4"] .k-fieldset .k-grid {
	grid-template-columns: repeat(1, 1fr)
}

.k-sections>.k-column[data-width="1/3"] .k-fieldset .k-grid .k-column,
.k-sections>.k-column[data-width="1/4"] .k-fieldset .k-grid .k-column {
	grid-column-start: initial
}

What’s funny is that it only prevents from you from setting field width when the parent column is 1/3 wide or 1/4 wide explicitly.

So, I tested it using 2/6 instead of 1/3 as the column width and it works.

Now this limit seems even more arbitrary and pointless.

6

Good catch, at least you got it to work. But yes, that seems pretty arbitrary.