Skip to content

Hide obsolete FontSize values from IDE autocomplete#33694

Merged
PureWeen merged 3 commits intodotnet:inflight/currentfrom
noiseonwires:hide-obsolete-fontsize-values
Jan 23, 2026
Merged

Hide obsolete FontSize values from IDE autocomplete#33694
PureWeen merged 3 commits intodotnet:inflight/currentfrom
noiseonwires:hide-obsolete-fontsize-values

Conversation

@noiseonwires
Copy link
Contributor

@noiseonwires noiseonwires commented Jan 23, 2026 •
edited
Loading

Description of Change

This PR hides obsolete FontSize named values (like "Large", "Medium", "Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked obsolete since .NET 9. However, the design-time type converter was still suggesting these values in the IDE's IntelliSense, leading users to use them and then receive "Obsolete" warnings - especially when using XAML source generation (MauiXamlInflator=SourceGen).

The fix overrides GetStandardValuesSupported() to return false and GetStandardValues() to return an empty collection in FontSizeDesignTypeConverter. This prevents the IDE from suggesting the obsolete named font size values while still allowing them to be used (with appropriate obsolete warnings) for backward compatibility.

Issues Fixed

#33560

see also: #33623

Copilot AI review requested due to automatic review settings January 23, 2026 16:51
@dotnet-policy-service dotnet-policy-service bot added the community ✨ Community Contribution label Jan 23, 2026
@dotnet-policy-service
Copy link
Contributor

dotnet-policy-service bot commented Jan 23, 2026

Hey there @@noiseonwires! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

Copilot AI reviewed Jan 23, 2026
View reviewed changes
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR prevents obsolete FontSize named values from appearing in IDE autocomplete by overriding the design-time type converter methods. The named font sizes (like "Large", "Medium", "Small") have been marked obsolete since .NET 9, but were still being suggested in IntelliSense, causing confusion when users received obsolete warnings after using them—especially with XAML source generation enabled.

Changes:

  • Overrides GetStandardValuesSupported() to return false, preventing IDE from requesting standard values
  • Overrides GetStandardValues() to return an empty collection as a defensive measure
  • Preserves IsValid() behavior to maintain backward compatibility, allowing existing code using obsolete values to continue working

noiseonwires and others added 2 commits January 23, 2026 18:09
@noiseonwires
Update src/Controls/src/Core.Design/FontSizeDesignTypeConverter.cs
e90b0f9 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
add unit tests
16a18d4
@PureWeen PureWeen changed the base branch from main to inflight/current January 23, 2026 23:01
@PureWeen PureWeen merged commit 12ced14 into dotnet:inflight/current Jan 23, 2026
1 of 2 checks passed
PureWeen pushed a commit that referenced this pull request Jan 27, 2026
@noiseonwires @PureWeen
Hide obsolete FontSize values from IDE autocomplete (#33694)
43474fc 
### Description of Change
This PR hides obsolete FontSize named values (like "Large", "Medium",
"Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked
[obsolete](https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.namedsize?view=net-maui-9.0)
since .NET 9. However, the design-time type converter was still
suggesting these values in the IDE's IntelliSense, leading users to use
them and then receive "Obsolete" warnings - especially when using XAML
source generation (MauiXamlInflator=SourceGen).

The fix overrides `GetStandardValuesSupported()` to return false and
`GetStandardValues()` to return an empty collection in
`FontSizeDesignTypeConverter`. This prevents the IDE from suggesting the
obsolete named font size values while still allowing them to be used
(with appropriate obsolete warnings) for backward compatibility.

### Issues Fixed

#33560

see also: #33623

---------

Co-authored-by: Kirill Ovchinnikov <kovchinnikov@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PureWeen pushed a commit that referenced this pull request Jan 29, 2026
@noiseonwires @PureWeen
Hide obsolete FontSize values from IDE autocomplete (#33694)
8b8e598 
### Description of Change
This PR hides obsolete FontSize named values (like "Large", "Medium",
"Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked
[obsolete](https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.namedsize?view=net-maui-9.0)
since .NET 9. However, the design-time type converter was still
suggesting these values in the IDE's IntelliSense, leading users to use
them and then receive "Obsolete" warnings - especially when using XAML
source generation (MauiXamlInflator=SourceGen).

The fix overrides `GetStandardValuesSupported()` to return false and
`GetStandardValues()` to return an empty collection in
`FontSizeDesignTypeConverter`. This prevents the IDE from suggesting the
obsolete named font size values while still allowing them to be used
(with appropriate obsolete warnings) for backward compatibility.

### Issues Fixed

#33560

see also: #33623

---------

Co-authored-by: Kirill Ovchinnikov <kovchinnikov@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PureWeen pushed a commit that referenced this pull request Feb 2, 2026
@noiseonwires @PureWeen
Hide obsolete FontSize values from IDE autocomplete (#33694)
75c7b27 
### Description of Change
This PR hides obsolete FontSize named values (like "Large", "Medium",
"Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked
[obsolete](https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.namedsize?view=net-maui-9.0)
since .NET 9. However, the design-time type converter was still
suggesting these values in the IDE's IntelliSense, leading users to use
them and then receive "Obsolete" warnings - especially when using XAML
source generation (MauiXamlInflator=SourceGen).

The fix overrides `GetStandardValuesSupported()` to return false and
`GetStandardValues()` to return an empty collection in
`FontSizeDesignTypeConverter`. This prevents the IDE from suggesting the
obsolete named font size values while still allowing them to be used
(with appropriate obsolete warnings) for backward compatibility.

### Issues Fixed

#33560

see also: #33623

---------

Co-authored-by: Kirill Ovchinnikov <kovchinnikov@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@PureWeen PureWeen mentioned this pull request Feb 3, 2026
Merged
github-actions bot pushed a commit that referenced this pull request Feb 4, 2026
@noiseonwires @PureWeen
Hide obsolete FontSize values from IDE autocomplete (#33694)
d1c4f55 
### Description of Change
This PR hides obsolete FontSize named values (like "Large", "Medium",
"Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked
[obsolete](https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.namedsize?view=net-maui-9.0)
since .NET 9. However, the design-time type converter was still
suggesting these values in the IDE's IntelliSense, leading users to use
them and then receive "Obsolete" warnings - especially when using XAML
source generation (MauiXamlInflator=SourceGen).

The fix overrides `GetStandardValuesSupported()` to return false and
`GetStandardValues()` to return an empty collection in
`FontSizeDesignTypeConverter`. This prevents the IDE from suggesting the
obsolete named font size values while still allowing them to be used
(with appropriate obsolete warnings) for backward compatibility.

### Issues Fixed

#33560

see also: #33623

---------

Co-authored-by: Kirill Ovchinnikov <kovchinnikov@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
github-actions bot pushed a commit that referenced this pull request Feb 8, 2026
@noiseonwires @PureWeen
Hide obsolete FontSize values from IDE autocomplete (#33694)
28a5f99 
### Description of Change
This PR hides obsolete FontSize named values (like "Large", "Medium",
"Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked
[obsolete](https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.namedsize?view=net-maui-9.0)
since .NET 9. However, the design-time type converter was still
suggesting these values in the IDE's IntelliSense, leading users to use
them and then receive "Obsolete" warnings - especially when using XAML
source generation (MauiXamlInflator=SourceGen).

The fix overrides `GetStandardValuesSupported()` to return false and
`GetStandardValues()` to return an empty collection in
`FontSizeDesignTypeConverter`. This prevents the IDE from suggesting the
obsolete named font size values while still allowing them to be used
(with appropriate obsolete warnings) for backward compatibility.

### Issues Fixed

#33560

see also: #33623

---------

Co-authored-by: Kirill Ovchinnikov <kovchinnikov@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PureWeen pushed a commit that referenced this pull request Feb 9, 2026
@noiseonwires @PureWeen
Hide obsolete FontSize values from IDE autocomplete (#33694)
a0a3f2a 
### Description of Change
This PR hides obsolete FontSize named values (like "Large", "Medium",
"Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked
[obsolete](https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.namedsize?view=net-maui-9.0)
since .NET 9. However, the design-time type converter was still
suggesting these values in the IDE's IntelliSense, leading users to use
them and then receive "Obsolete" warnings - especially when using XAML
source generation (MauiXamlInflator=SourceGen).

The fix overrides `GetStandardValuesSupported()` to return false and
`GetStandardValues()` to return an empty collection in
`FontSizeDesignTypeConverter`. This prevents the IDE from suggesting the
obsolete named font size values while still allowing them to be used
(with appropriate obsolete warnings) for backward compatibility.

### Issues Fixed

#33560

see also: #33623

---------

Co-authored-by: Kirill Ovchinnikov <kovchinnikov@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
github-actions bot pushed a commit that referenced this pull request Feb 9, 2026
@noiseonwires @PureWeen
Hide obsolete FontSize values from IDE autocomplete (#33694)
035c04f 
### Description of Change
This PR hides obsolete FontSize named values (like "Large", "Medium",
"Small", etc.) from IDE autocomplete suggestions in XAML.

The named font size values have been marked
[obsolete](https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.namedsize?view=net-maui-9.0)
since .NET 9. However, the design-time type converter was still
suggesting these values in the IDE's IntelliSense, leading users to use
them and then receive "Obsolete" warnings - especially when using XAML
source generation (MauiXamlInflator=SourceGen).

The fix overrides `GetStandardValuesSupported()` to return false and
`GetStandardValues()` to return an empty collection in
`FontSizeDesignTypeConverter`. This prevents the IDE from suggesting the
obsolete named font size values while still allowing them to be used
(with appropriate obsolete warnings) for backward compatibility.

### Issues Fixed

#33560

see also: #33623

---------

Co-authored-by: Kirill Ovchinnikov <kovchinnikov@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PureWeen added a commit that referenced this pull request Feb 10, 2026
@PureWeen
February 10th, Candidate (#33779)
00b06e5 
.NET MAUI inflight/candidate introduces significant improvements across
all platforms with focus on quality, performance, and developer
experience. This release includes 20 commits with various improvements,
bug fixes, and enhancements.


## Blazor
- Fix for BlazorWebView Back Navigation Issues on Android 13+ After
Predictive Back Gesture Changes by @SuthiYuvaraj in
#33213
  <details>
  <summary>🔧 Fixes</summary>

- [Back navigation different between .net 9 and .net 10 blazor
hybrid](#32767)
  </details>

## CollectionView
- [Android] Fix for CollectionView.EmptyView does not remeasure its
height when the parent layout changes dynamically, causing incorrect
sizing. by @BagavathiPerumal in
#33559
  <details>
  <summary>🔧 Fixes</summary>

- [`CollectionView.EmptyView` does not remeasure its height when the
parent layout changes dynamically, causing incorrect
sizing.](#33324)
  </details>

- [Android] Fixed CollectionView reordering last item by @vitalii-vov in
#17825
  <details>
  <summary>🔧 Fixes</summary>

- [Android app crashes when dragging into
CollectionView](#17823)
  </details>

## DateTimePicker
- [iOS] Fix VoiceOver focus not shifting to Picker/DatePicker/TimePicker
popups by @kubaflo in #33152
  <details>
  <summary>🔧 Fixes</summary>

- [Voiceover does not automatically shift focus to the "Category" popup
when it opens.: A11y_Developer balance version .NET
10_Project_ScreenReader](#30746)
  </details>

## Dialogalert
- [iOS 26] Fix DisplayPromptAsync maxLength not enforced due to new
multi-range delegate by @Shalini-Ashokan in
#33616
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS 26.1] DisplayPromptAsync ignores maxLength and does not respect
RTL FlowDirection](#33549)
  </details>

## Flyout
- [iOS] Shell: Account for SafeArea when positioning flyout footer by
@kubaflo in #32891
  <details>
  <summary>🔧 Fixes</summary>

- [[IOS] Footer not displaying in iOS when StackOrientation.Horizontal
is set on FlyoutFooter](#26395)
  </details>

## Fonts
- Hide obsolete FontSize values from IDE autocomplete by @noiseonwires
in #33694

## Gestures
- Android pan fixes by @BurningLights in
#21547
  <details>
  <summary>🔧 Fixes</summary>

- [Flickering occurs while updating the width of ContentView through
PanGestureRecognizer.](#20772)
  </details>

## Navigation
- Shell: Add duplicate route validation for sibling elements by
@SubhikshaSf4851 in #32296
  <details>
  <summary>🔧 Fixes</summary>

- [OnNavigatedTo is not called when navigating from a specific
page](#14000)
  </details>

## Picker
- Improved Unfocus support for Picker on Mac Catalyst by @kubaflo in
#33127
  <details>
  <summary>🔧 Fixes</summary>

- [When using voiceover unable to access expanded list of project combo
box: A11y_.NET maui_user can creat a tak_Screen
reader](#30897)
- [Task and Project controls are not accessible with keyboard:A11y_.NET
maui_User can create a new
task_Keyboard](#30891)
  </details>

## SafeArea
- [iOS] SafeArea: Return Empty for non-ISafeAreaView views (opt-in
model) by @praveenkumarkarunanithi in
#33526
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] SafeArea is not applied when a ContentPage uses a
ControlTemplate](#33458)
  </details>

## Shell
- [iOS] Fix ObjectDisposedException in TraitCollectionDidChange on
window disposal by @jeremy-visionaid in
#33353
  <details>
  <summary>🔧 Fixes</summary>

- [Intermittent crash on exit on MacCatalyst -
ObjectDisposedException](#33352)
  </details>

- [Issue-Resolver] Explicit fallback for BackButtonBehavior lookup by
@kubaflo in #33204
  <details>
  <summary>🔧 Fixes</summary>

- [Setting BackButtonBehavior to not visible or not enabled does not
work](#28570)
- [BackButtonBehavior not
bound](#33139)
  </details>

## Templates
- [Templates] Remove redundant SemanticProperties.Description attribute
by @kubaflo in #33621
  <details>
  <summary>🔧 Fixes</summary>

- [Task and Project controls are not accessible with keyboard:A11y_.NET
maui_User can create a new
task_Keyboard](#30891)
- [Unable to select "Tags" when Voiceover is turned on.: A11y_Developer
balance version .NET
10_Project_ScreenReader](#30749)
  </details>

## Theme
- [Windows] Fix runtime theme update for controls and TitleBar by
@Tamilarasan-Paranthaman in #31714
  <details>
  <summary>🔧 Fixes</summary>

- [[Windows][MacOS?] Change title bar color when switching light/dark
theme at runtime](#12507)
- [OS system components ignore app
theme](#22058)
- [[Mac Catalyst][Windows] TitleBar not reacting on UserAppTheme
changes](#30518)
- [In dark theme "Back" and "hamburger" button icon color contrast with
background color is less than 3:1: A11y_.NET maui_User can get all the
insights of Dashboard_Non text
Contrast](#30807)
- [`Switch` is invisible on `PointOver` when theme has
changed](#31819)
  </details>

## Theming
- [XSG] Fix Style Setters referencing source-generated bindable
properties by @simonrozsival in
#33562

## Titlebar
- [Windows] Fix TitleBar.IsVisible = false the caption buttons become
unresponsive by @devanathan-vaithiyanathan in
#33256
  <details>
  <summary>🔧 Fixes</summary>

- [When TitleBar.IsVisible = false the caption buttons become
unresponsive on Windows](#33171)
  </details>

## WebView
- Fix WebView JavaScript string escaping for backslashes and quotes by
@StephaneDelcroix in #33726

## Xaml
- [XSG] Fix NaN value in XAML generating invalid code by
@StephaneDelcroix in #33533
  <details>
  <summary>🔧 Fixes</summary>

- [[XSG] NaN value in XAML generates invalid
code](#33532)
  </details>


<details>
<summary>📦 Other (1)</summary>

- Remove InternalsVisibleTo attributes for .NET MAUI Community Toolkit
by @jfversluis via @Copilot in #33442

</details>
**Full Changelog**:
main...inflight/candidate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@StephaneDelcroix StephaneDelcroix StephaneDelcroix approved these changes

Assignees

No one assigned

Labels

community ✨ Community Contribution

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@noiseonwires @StephaneDelcroix @PureWeen

Comments