Type of issue
Other (describe below)
Description
The HTML template used for documentation on most pages leaves a lot to be desired. The width of the middle section is completely inadequate for displaying code. If you're lucky, then the horizontal scroll bar is in view for your usage. If not... you're trapped in a scrolling nightmare. I propose that the width of the middle section should be adjustable based on content. Ideally, this should be automatically done by the page creators, but it could be user-controlled on a per-page basis or via settings. If you prefer not to do that, then at least buttons or other artifacts should be provided to automate scrolling left and right.
Page URL
https://learn.microsoft.com/en-us/dotnet/api/system.threading.tasks.taskscheduler?view=net-10.0
Content source URL
https://github.com/dotnet/dotnet-api-docs-temp/blob/live/xml/System.Threading.Tasks/TaskScheduler.xml
Document Version Independent Id
704b8fe0-da95-8a3f-da04-5092c2d8d200
Platform Id
f00f49e1-55f5-e07a-7fe8-dca2a7aa8397
Article author
@dotnet-bot
Type of issue
Other (describe below)
Description
The HTML template used for documentation on most pages leaves a lot to be desired. The width of the middle section is completely inadequate for displaying code. If you're lucky, then the horizontal scroll bar is in view for your usage. If not... you're trapped in a scrolling nightmare. I propose that the width of the middle section should be adjustable based on content. Ideally, this should be automatically done by the page creators, but it could be user-controlled on a per-page basis or via settings. If you prefer not to do that, then at least buttons or other artifacts should be provided to automate scrolling left and right.
Page URL
https://learn.microsoft.com/en-us/dotnet/api/system.threading.tasks.taskscheduler?view=net-10.0
Content source URL
https://github.com/dotnet/dotnet-api-docs-temp/blob/live/xml/System.Threading.Tasks/TaskScheduler.xml
Document Version Independent Id
704b8fe0-da95-8a3f-da04-5092c2d8d200
Platform Id
f00f49e1-55f5-e07a-7fe8-dca2a7aa8397
Article author
@dotnet-bot