In the past I was able to group an image with a white background select hidden in metrics inspector content overflow and give it radius in the element inspector of say 10px it worked. Now It looks like in order for it to work, I have to go back to metrics inspector select visible and then hidden to see it work, In other words, It doesn't register my first attempt at hiding content overflow.
That does not actually answer the question But its does do this on M1-Sequoia.15.2
Done in this order of steps 1:
Adding an image,
Grouping image,
Changing radius on group.
Setting Hidden on group
The live update to the group does not happen.
This is the case for both IDE and Preview/Export.
Done in this order of steps 2:
Adding an image,
Grouping image,
Setting Hidden on group,
Changing radius on group.
The live update to the group works.
This is the case for both IDE and Preview/Export.
For steps 1
I would call this an unexpected behaviour, I would expect the group to respect the radius hidden or not when hidden is set after radius changes.
Thanks for reporting this issue. It doesn't actually surprise me as a rendering bug, but I can't seem to reproduce it with what I think are the steps you're reporting.
If you have a minute, would you mind sending me a zip of a .hype document that reproduces the problem (maybe it is image related?) along with a quick screen capture so I can see your steps? Thanks much!
Thanks @MarkHunte, but I still can't seem to reproduce an issue.
Just to note, it is not a bug that having content-overflow as visible does not clip on the border radius. This is just how (all) browsers render this.
It sounds like @petester was reporting an issue where when the content overflow is hidden, radius updates are not being shown. The workaround seems to be togging content-overflow from hidden to visible and back to hidden. Is that correct? If so I still cannot repro this, but would love to see a screen capture from start to finish in action on what you're doing.
Ah, thanks so much! I can reproduce it now. It looks like the issue is one of going from a 0 value while hidden to something else.
This one is fallout from a macOS 14.4 bug where we disabled webkit graphics acceleration in the scene editor. (There's a hidden pref that could turn it back on, but realistically this will cause more problems than it is worth right now).
There's another rendering bug with likely a similar cause that I'm investigating now, so hopefully the fix will be the same.