Chromium fork named after radioactive element No. 90. Windows and MacOS/Raspi/Android/Special builds are in different repositories, links are towards the top of the README.md.
Problem
Clip-path visual inconsistency / choppy when hardware acceleration flag is enabled. When it is disabled, the visual is correct and smooth, but the rendering of the page and animations are slow (obviously).
Screenshots
Chrome 126.0.6478.62
Thorium 124.0.6367.218
Safari 17.5
Additional Notes
Here's a copy of the CSS that enables that diagonal look (adds a slanted effect at the top of a div, for example) : clip-path: polygon(0% 5.78125vw, 100% 0%, 100% 100%, 0% 100%);
Here's the spec of my MacBook Pro.
The problem happens regardless of the active graphic card enabled (discrete graphics with the Radeon or not). It was documented on Sonoma before updating my machine to the latest MacOS beta - I wanted to see if it was some internal core graphics shenanigans, but it still happens on Sequoia beta 1.
System Details
Problem Clip-path visual inconsistency / choppy when hardware acceleration flag is enabled. When it is disabled, the visual is correct and smooth, but the rendering of the page and animations are slow (obviously).
Screenshots Chrome 126.0.6478.62
![chrome-x86_64-126 0 6478 62](https://github.com/Alex313031/thorium/assets/412352/83421185-f110-47e2-b8ee-72a5965d8418)
Thorium 124.0.6367.218![thorium-124 0 6367 218](https://github.com/Alex313031/thorium/assets/412352/070df69a-d256-4dc9-aeca-bd8404358ddd)
Safari 17.5![safari-17 5](https://github.com/Alex313031/thorium/assets/412352/437496ab-2d0f-4661-8e94-8eb6475597bb)
Additional Notes Here's a copy of the CSS that enables that diagonal look (adds a slanted effect at the top of a div, for example) : clip-path: polygon(0% 5.78125vw, 100% 0%, 100% 100%, 0% 100%);
Here's the spec of my MacBook Pro.![Capture d’écran, le 2024-06-17 à 23 23 23](https://github.com/Alex313031/thorium/assets/412352/69b77099-c0d7-481c-aa2b-1cac5976205b)
The problem happens regardless of the active graphic card enabled (discrete graphics with the Radeon or not). It was documented on Sonoma before updating my machine to the latest MacOS beta - I wanted to see if it was some internal core graphics shenanigans, but it still happens on Sequoia beta 1.