Repository navigation
Conversation
This was referenced Oct 15, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
M2.14 Browser field UX: whole-row navigation and explicit selected DO reads
Direct base: Draft #583
756de98a2bb0(retains #582 GOOSE and TapChg repair, live title, icons, prior A/B safety and 2,002 regression baseline). PR remains Draft and all ancestors are untouched.Root causes fixed
IedBrowserReadPlanand read service, no second client, no cyclic poll. If no DO focused, existing LN-wide Read remains. Read All remains global and unchanged.ReadObjectReference, never a preferred process leaf or inferred name. Model identity is constrained to the active selected LN. Focus is cleared on page navigation.Safety / acceptance
No automatic read on navigation, control/GI/GOOSE activation, write, MMS runtime changes, RCB, engine pin or stable/main modifications. Windows exact-SHA CI + device acceptance required. If IED rejects individual reads, unavailable stays truthful: a click or model declaration never fabricates remote values.