Stefano Milani
02/10/2025, 9:26 AMbod
02/10/2025, 10:27 AMStefano Milani
02/10/2025, 12:08 PMbod
02/10/2025, 12:09 PMStefano Milani
02/10/2025, 12:55 PMChrimaeon
02/10/2025, 1:43 PMStefano Milani
02/10/2025, 1:55 PMChrimaeon
02/10/2025, 2:06 PMStefano Milani
02/10/2025, 2:07 PMChrimaeon
02/10/2025, 2:10 PMืืืืื ืืืก
02/10/2025, 2:25 PMืืืืื ืืืก
02/10/2025, 2:25 PMืืืืื ืืืก
02/10/2025, 2:26 PMStefano Milani
02/10/2025, 2:27 PMืืืืื ืืืก
02/10/2025, 2:28 PMStefano Milani
02/10/2025, 2:58 PMืืืืื ืืืก
02/10/2025, 3:59 PMืืืืื ืืืก
02/10/2025, 4:00 PMStefano Milani
02/10/2025, 4:03 PMRok Oblak
02/11/2025, 5:30 PMSkaldebane
02/12/2025, 4:48 AMBlendMode.Clear
(which will create a hole in the canvas)...
Never tried this before, but that would (theoretically) allow overlaying things on top. However any click events are probably gonna be consumed by the canvas, not sure if there's a way around that.Rok Oblak
02/12/2025, 5:40 AMSkaldebane
02/12/2025, 1:04 PMBlendMode.Clear
is that it doesn't care what's behind your composable (parent, other siblings, etc...), it will clear everything behind it! (it removes both the destination and target).
But yeah, the issue of edge cases will still exist, for example a semi-transparent HTML elementSkaldebane
02/12/2025, 6:18 PMBlendMode.Clear
using drawBehind
modifier. It clears everything behind it, and since <canvas>
is transparent by default, we can see the HTML background through it.ืืืืื ืืืก
02/15/2025, 4:48 PMBlendMode.Clear
(which will create a hole in the canvas)...
>
> Never tried this before, but that would (theoretically) allow overlaying things on top. However any click events are probably gonna be consumed by the canvas, not sure if there's a way around that.
@Skaldebane I will try! Thank you very much for the adviceืืืืื ืืืก
02/15/2025, 5:46 PMืืืืื ืืืก
02/15/2025, 5:51 PMืืืืื ืืืก
02/15/2025, 6:06 PMSkaldebane
02/15/2025, 6:57 PMืืืืื ืืืก
02/15/2025, 6:59 PMSkaldebane
02/15/2025, 7:00 PMSkaldebane
02/15/2025, 7:01 PMWindow
).ืืืืื ืืืก
02/15/2025, 7:02 PMืืืืื ืืืก
02/15/2025, 7:03 PMืืืืื ืืืก
02/15/2025, 7:04 PMThough you can (potentially) apply a similar solution to the one on web; but I'm not sure how to go about that (how to create a swing panel behind the Compose panel that's automatically created byI don't know either.).Window
Skaldebane
02/15/2025, 7:04 PMSkaldebane
02/15/2025, 7:04 PMืืืืื ืืืก
02/15/2025, 7:05 PMืืืืื ืืืก
02/15/2025, 7:06 PMืืืืื ืืืก
02/15/2025, 7:08 PMSkaldebane
02/15/2025, 7:09 PMืืืืื ืืืก
02/15/2025, 7:10 PMYeah, that'd be great, and is the most practical thing for them to support short-term.For me, it would just be to correct the slightly long start-up times.
ืืืืื ืืืก
02/15/2025, 8:33 PMChrimaeon
02/16/2025, 3:31 PMืืืืื ืืืก
02/16/2025, 3:32 PMChrimaeon
02/16/2025, 3:33 PMSkaldebane
02/16/2025, 3:33 PMืืืืื ืืืก
02/16/2025, 3:33 PMChrimaeon
02/16/2025, 3:34 PMืืืืื ืืืก
02/16/2025, 3:35 PMืืืืื ืืืก
02/16/2025, 3:35 PMSkaldebane
02/17/2025, 1:38 AMCompositingStrategy.Offscreen
(which itself has a parent that draws something behind it).
For example, a parent that applies the alpha
Modifier uses has the Offscreen
compositing strategy, as well as applying a RenderEffect
.
Not sure if this is worth "fixing"; users who fall into this (if ever) can workaround this themselves by taking the position of the video composable, and applying another BlendMode.Clear
above the Modifier that caused offscreen compositing.
(probably would be most likely caused by stuff like AnimatedVisibility / AnimatedContent? It would simply cause the video to disappear once the animation starts in case of disappearance, and appear once the animation ends in case of appearance, afaik)Stefano Milani
02/17/2025, 7:40 AMืืืืื ืืืก
03/30/2025, 5:07 AMAll these work on iOS safariCheck now, it must work on safari