-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: FauxGradientBorderPresenter
control
#7649
feat: FauxGradientBorderPresenter
control
#7649
Conversation
I guess this is required to implement the new Fluent v2 borders on all platforms such as Wasm? If so, what is this going to do to the visual tree? I would not usually expect Uno to inject custom controls like this on standard input elements like TextBox. Edit: I guess my point is the LinearGradientBrush itself should have these types of hacks in my opinion - perhaps a new Uno-specific property to enable them. |
898c14f
to
c31abdb
Compare
The build 38665 found UI Test snapshots differences: Details
|
c31abdb
to
ae24ea1
Compare
The build 38708 found UI Test snapshots differences: Details
|
@robloo I agree that it would be preferrable if the specific behavior were encapsulated within the |
ae24ea1
to
d48e1c1
Compare
The build 38809 found UI Test snapshots differences: Details
|
FauxGradientBottomBorder
controlFauxGradientBottomBorder
control
6e70b47
to
3687dfb
Compare
...esApp/UITests.Shared/Microsoft_UI_Xaml_Controls/RatingControlTests/RatingControlPage.xaml.cs
Outdated
Show resolved
Hide resolved
268e4c8
to
2a65cbb
Compare
FauxGradientBottomBorder
controlFauxGradientBorderPresenter
control
@jeromelaban @carldebilly I noticed the |
Definitely sounds plausible indeed. |
The build 40684 found UI Test snapshots differences: Details
|
ce6fe30
to
b5afbf2
Compare
…r unconditionally
a7e3111
to
acf61f2
Compare
|
GitHub Issue (If applicable): closes #7621, closes #7110
PR Type
What kind of change does this PR introduce?
Future improvements
Border.iOSmacOS.cs
- See whetherUpdateBorderPartial() => this.SetNeedsDisplay();
is actually neededWhat is the current behavior?
Current solution for fake gradient borders on WinUI 2.6 had several downsides:
What is the new behavior?
Using a new internal control to render the border based on current settings of
BorderBrush
,BorderThickness
andCornerRadius
.PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.