starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Task: Refactor IRenderData and create IAccessibilityData #2798

New Issue
Closed
opened 2026-01-30 23:05:24 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 23:05:24 +00:00
Owner
Copy Link

Originally created by @carlos-zamora on GitHub (Jul 16, 2019).

Originally assigned to: @carlos-zamora on GitHub.

A TODO for after PR #1915

IRenderData is supposed to be read-only, acting only as a method of querying the state of the terminal/console. The methods added in the PR may change the state.

We should try and separate out what we need for accessibility into a new interface: IAccessibilityData

In my mind, I'd like it if the relationship between IRenderData and the necessary accessibility functions (IAccessibilityData) would look something like this:

IBaseData
├─ IRenderData
└─ IAccessibilityData

  • IBaseData would provide a limited view for what IAccessibilityData needs from IRenderData
  • IRenderData would look the same
  • IAccessibilityData would get these functions that I added here (that would alleviate your concern)
Originally created by @carlos-zamora on GitHub (Jul 16, 2019). Originally assigned to: @carlos-zamora on GitHub. A TODO for after PR #1915 `IRenderData` is supposed to be read-only, acting only as a method of querying the state of the terminal/console. The methods added in the PR may change the state. We should try and separate out what we need for accessibility into a new interface: `IAccessibilityData` In my mind, I'd like it if the relationship between `IRenderData` and the necessary accessibility functions (`IAccessibilityData`) would look something like this: `IBaseData` ├─ `IRenderData` └─ `IAccessibilityData` - `IBaseData` would provide a limited view for what `IAccessibilityData` needs from `IRenderData` - `IRenderData` would look the same - `IAccessibilityData` would get these functions that I added here (that would alleviate your concern)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Accessibility Area-CodeHealth Issue-Task Needs-Tag-Fix Product-Conhost Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2798
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?