Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NativeScript/NativeScript
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: NativeScript/NativeScript
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fix/gradient-stop-defaults
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 4 files changed
  • 1 contributor

Commits on Sep 3, 2026

  1. fix(core): resolve gradient stop positions the way CSS does 

    A linear-gradient stop without a position was handed to the platform as
missing. Android's float[] left it at 0, so `#fff 68%, #f4f4f5` rendered
as a hard edge at 68% instead of a ramp to the end; iOS passed a shorter
locations array than colors and let CAGradientLayer guess.

Resolve positions once, per CSS: a first stop without a position sits at
0, a last one at 1, runs of unpositioned stops spread evenly between their
positioned neighbours, and a position lower than one before it is raised
to that value. Both platforms now receive a complete, monotonic list.
    @NathanWalker
    NathanWalker committed Sep 3, 2026
    Configuration menu
    Copy the full SHA
    6c80db3 View commit details
    Browse the repository at this point in the history
Loading