UIK 5104/scroll-bar-issues-in-safari#2868
Merged
Valeria-Zimnitskaya merged 7 commits intorelease/v17from Apr 14, 2026
Merged
Conversation
## Changelog ### @semcore/grid #### Break - New major version. ### @semcore/flex-box #### Break - New major version. ### @semcore/neighbor-location #### Break - New major version. ### @semcore/popper #### Break - New major version. ### @semcore/icon #### Break - New major version. ### @semcore/illustration #### Break - New major version.
## Changelog ### @semcore/base-tigger #### BREAK - Removed old implementation for the `LinkTrigger`. This is a wrapper for the `ButtonLink` now. ### @semcore/button #### BREAK - Removed old implementation for the `ButtonLink`. This is a wrapper for the `Link` but in tag `button` now. ### @semcore/link #### BREAK - This is now an inline element. The inline property is no longer applicable. - `noWrap` is now false by default. - `hintPlacement` property added. - Link.Text is now a Text element; all text customization should be done within it. Link is simply a container. ### @semcore/breakpoints #### BREAK - New major version. ### @semcore/grid #### BREAK - New major version. ### @semcore/flex-box #### BREAK - New major version. ### @semcore/neighbor-location #### BREAK - New major version. ### @semcore/popper #### BREAK - New major version.
…ent Safari ghost rendering
ilyabrower
approved these changes
Apr 14, 2026
…ent Safari ghost rendering
….com:semrush/intergalactic into UIK-5104/scroll-area-slider-gpu-cache-issues
Valeria-Zimnitskaya
approved these changes
Apr 14, 2026
Valeria-Zimnitskaya
deleted the
UIK-5104/scroll-area-slider-gpu-cache-issues
branch
j-mnizhek
pushed a commit
that referenced
this pull request
Apr 16, 2026
## Changelog ### @semcore/base-components #### Fixed - **scroll-area** Fixed scroll bar slider leaving visual artifacts in Safari after being hidden. <!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context ## How has this been tested? Manually ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Co-authored-by: ilia.brauer <ilia.brauer@semrush.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog
@semcore/base-components
Fixed
Motivation and Context
How has this been tested?
Manually
Screenshots (if appropriate):
Types of changes
Checklist: