Fabric 7.0 Planning

[micahgodbolt]

Project: 7.0 Release

View and try fabric@next builds on Fabric React Demos

Cross-project tasks

Upgrades

• Upgrade to React 16.8.3 - Upgrade to React 16.8.3 #8041
• Upgrade to TypeScript 3.3.3 - Upgrade to TypeScript 3.3.3 #8040

Theming

• Default to Fluent theme - Default to Fluent theme #8038 - In progress (27/42)

Packages

• Create "legacy" package - Create legacy components package #8626

Deprecation

• Remove use of deprecated lifecycle methods - Fix deprecated lifecycle methods #8743
• Use new context API - Convert ScrollablePane to new context API #7365 Convert ResizeGroup to new context API #7364 Convert Sticky to new context API #7366 ScrollContainer and VirtualizedList experiments are using legacy context API #7368

API

• Modify slots API - API Breaking Changes for Fabric 7 #8328

Targeted fixes

Controls

• Slider: Remove deprecated types and make controllable - Fix up slider component #8576
• Nav: Move to legacy package - Move Nav to legacy components package #8627

Testing

• Validate test debugging in fabric 7

Cut

• Remove deprecated APIs - Remove deprecated APIs #8042 - pushed to next release
• Separate base theme into own package - Separate base theme into own package #8039 - wontfix

[lafe]

If you increase the minimum versions like that, please ensure that the SharePoint Framework also supports these versions (On Premises and Online). Currently, SPFx uses React 16.3 and TypeScript 2.4.2.

[MLoughry]

Is there an issue tracking not using hard-coded colors in a few of the Fluent styles (eg., DefaultButton).

This is currently a blocker for Outlook Web even dogfooding Fluent themes. Fluent should not be made the default in 7.0 so long as this is still an issue.

[micahgodbolt]

@Vitalius1 are you familiar with those fluent styles?

[Vitalius1]

@micahgodbolt #8098 should solve all the issues @MLoughry mentioned.

[khmakoto]

Closing this as Fabric 7.0 has been out for a while.