Components size is wrongly calcucated

ba655d45b7de47cd816fad4960c86979cfd3e9ef_2_588x500
@brunofierens ? This is YOUR screenshot with the defect marked.

I clearly misunderstood. The devil is in the details. Sorry.
I will look to allocate time to investigate this deeper.

I tested this once more today.
With several browsers, several browser scales, different screen DPIs, ...

Try on mobile phone- just as I asked. On PC- maybe in private mode?

@brunofierens i remind you about thic topic again. Try on mobile phone- just as I asked.

We could do an improvement related to using a TWebPageControl with ShowTabs = false.
This improvement will be in the next release.

OK, but I'm sure it is independent of ShowTabs. The bug occurs on the vast majority of phones (I set ShowTabs = True).

I could clearly see a relationship with ShowTabs!

@brunofierens The problem still persists, a.o: Motorola G52, Xiaomi Redmi Note 12, Oneplus 9, Google Pixel 7, Samsung Galaxy a34. Latest version TMS WEB Core.





@brunofierens when will there be a fix?

On all browsers I can debug on, this can not be reproduced.
Other ways to see result on these specific browsers have limited to no debugging capabilities and as such, I have not been succesful at finding what is happening nor find a solution.

I think it is related to the align property and child-parent relationship. Can you add a dependency so that a child element can't be wider than its parent? If I'm not mistaken, you have a mechanism for calculating the size of components.

No, the only relation I could see so far is that the content within the tab area forces the tab area to stretch.

I'm not convinced. Look, in 1.jpg I set the "pnlBottom" to alTop- everything is ok. On 2.jpg I set alBottom- I get closer (110%) and it breaks. One more thing I noticed - it concerns nested components. If you don't know how to fix it, then add the fix I requested in the previous post.


What fix in what post?

Calculated size of child element cannot be wider than its parent element when using align. This will not remove the source of the bug, but it will fix the problem.

Did you read/understand the behavior I observed?!

What content? The panel contains only a button with a short inscription. I did not use tabs for the last example.

@brunofierens And what next, will you do anything? have you read with understanding what the problems are? Have you noticed that the component size problem also occurs without using pages? What about my repair proposal? Nothing has been corrected, but you avoid the topic and overuse the exclamation mark. You posted a screenshot and didn't even notice that you managed to repeat the bug (but you apologized). The problem is easy to replicate with the help of emulator sites.

I'm not avoiding the topic! We already spent days and days on this.
I spent more hours today and found something related to mobile browser scrollbar width calculation. I applied a fix and at least on the few devices where I could reproduce this, it looks better now. This fix (workaround) will be in the next release.