Road to MarkdownTextBlock 8.3 stable release

[Arlodotexe]

Background

The new and improved MarkdownTextBlock currently sits in WCT Labs, with several issues open and several fixes in PR.

Problem

There's an increasing need for a reliable, extensible and maintainable MarkdownTextBlock control, especially with the rise of new applications using generative AI.

We'd like to give priority and focus to this control, aiming to graduate it from Labs for the WCT 8.3 stable release.

Solution

There's significant work to do in order to stabilize this control enough for production-ready release.

Generally, we need to track:

• Bugs and issues
• Samples and documentation
• Tests and expected coverage
• Expected inbox behaviors and configurations
• Expected points of extensibility (ColorCode, custom renderers, etc)
• Expected MultiTarget support (uwp, wasdk, wasm, etc)

We can use this ticket to plan and track areas of interest for the 8.3 stable release.

Where needed, subtickets can be created to split up then group the work to avoid clutter here.

Existing tickets should be linked here or under an appropriate subticket.

[michael-hawker]

Reminder we have this view for experiments as well: Toolkit 8.x (view) - I added DataTable and MarkdownTextBlock to our parent experiment field that we were missing as well, so we should be able to add the subissues here to the board there as well.

[michael-hawker]

Note to that this is the original experiment tracking issue, so I think we should just be consolidating this all there vs. having a separate one here? #606 Or at least maybe the sub-issues if we just want to have this one tracking release bits/issues.

[Arlodotexe]

so I think we should just be consolidating this all there vs. having a separate one here

This ticket is for tracking our plans for 8.3. Sub-issues can't have multiple parents, but we're still well-sorted here. The parent of this ticket is the original MarkdownTextBlock experiment ticket which holds our backlog and per-version plans for that component (e.g. this 8.3 ticket).

We should have full visibility from the original ticket, bucketing tickets into per-version tracking like this shouldn't be hiding them from us.