docs(picker-legacy): remove legacy component

[thetaPC]

Issue URL: internal

What is the current behavior?

ion-picker-legacy and ion-picker-legacy-column are still being documented. They are components that have been deprecated in v8.

What is the new behavior?

• Removed docs related to those components for v9

Does this introduce a breaking change?

• Yes

• No

• ion-picker-legacy and ion-picker-legacy-column have been removed from Ionic Framework. The legacy picker component has been replaced with a inline picker component.

  • Usages such as ion-picker-legacy or IonPickerLegacy should be changed to ion-picker and IonPicker, respectively.

Other information

• Updating from Ionic 8 to 9
• Config

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ionic-docs	Ready	Preview, Comment	Apr 16, 2026 2:55am

[brandyscarney]

Suggested change

	1. Remove any usages of the `ion-picker-legacy` and `ion-picker-column-legacy` components. These components have been removed in Ionic 9. Use [`ion-picker` component](../api/picker.md#picker-in-modal) instead.
	1. Remove any usages of the `ion-picker-legacy` and `ion-picker-column-legacy` components. These components have been removed in Ionic 9. Use the [Picker](../api/picker.md) component instead.

Did you mean to target the picker-in-modal hash?

[thetaPC]

Yes, since that is the exact way to mimic what it would have been with the legacy picker. I wanted devs to be able to see the example and just replace it without having to figure it out on their own.

[brandyscarney]

Got it 👍

[thetaPC]

I left the link pointing to the Picker in Modal section. Let me know if you prefer that I don't do that. 2ce6f34

[brandyscarney]

Do we need to remove these here also: https://ionicframework.com/docs/developing/config#ionicconfig

[ShaneK]

Looking good! A couple of minor things

[ShaneK]

Two things on this line:

First, ion-picker-column-legacy should be ion-picker-legacy-column. The component directory is picker-legacy-column/ and the framework's BREAKING.md uses the correct order, so anyone grepping their templates with this spelling won't find what they're migrating off.

Second, should this note also call out the other removed surface? pickerController, useIonPicker (React), and the PickerOptions / PickerButton / PickerColumn / PickerColumnOption type exports are all gone from the framework packages in #31078. Controller and hook users will hit build errors and the current note only hints at renaming the element. If you do expand this to cover them, the framework's BREAKING.md entry should get the same treatment so the two sides stay in sync.