No formatting on linked spell windows from character sheet (3.5E)

[Zarestia]

Tried to overcome this with an extension, to no avail.

Ruleset: 3.5E
Extensions: None
FGU: Up to date (Live Channel)
Campaign: New

Steps to reproduce:
- Create a new character
- Create a new spellcasting class under 'actions'
- Add a Spell from a module or homebrew with formatted text to the spellcasting class (i.e. italic, bold, tables, etc.)
- Open the link of the newly added spell
- See thta the linked spell window has no formatting at all

In 5E the powers respect formatting and looks of the window. It would be really nice, if the same could work in 3.5E :)

See attached images for better visibility.

[bmos]

This is known and there is not currently an official plan to fix it. (https://www.fantasygrounds.com/forums/showthread.php?58000-Actions-tab-spell-description-formatting)
However, here is an extension I made which allows formatted text in the actions tab spell descriptions:
https://www.fantasygrounds.com/forums/showthread.php?60120-PFRPG-Spell-Description-Formatting

[Zarestia]

This is known and there is not currently an official plan to fix it. (https://www.fantasygrounds.com/forums/showthread.php?58000-Actions-tab-spell-description-formatting)
However, here is an extension I made which allows formatted text in the actions tab spell descriptions:
https://www.fantasygrounds.com/forums/showthread.php?60120-PFRPG-Spell-Description-Formatting

Sadly, can't have everything.
I already implemented part of your extension, works like a charm :D
Maybe we can have things like this native in the future for the bit lesser played rulesets :)

[bmos]

Sadly, can't have everything.
I already implemented part of your extension, works like a charm :D
Maybe we can have things like this native in the future for the bit lesser played rulesets :)
Pathfinder 1e/3.5E is the second-most played ruleset, we aren't THAT small :P
The main concern here that was voiced in that thread was backwards compatibility (which I have solved in my extension).
It's not out of the question that we might see it natively supported eventually.

Is there anything that my extension isn't fixing about the situation?