LogUI 1.2 Fixes Log-Entry Selection and Focus in macOS 27

LogUI 1.2 addresses a small but disruptive interaction problem in Golden Gate: selecting a log entry now moves focus with the selection, so the row can be highlighted as a whole. The update is a targeted workaround rather than a broad redesign, but it removes a keyboard detour that made a basic browsing action feel broken.

The problem affected LogUI 1.1. Clicking an entry selected it without moving focus to the same row. As a result, the entry wasn’t highlighted in full colour, and users had to press Tab and Shift-Tab to move focus separately until the visual highlight appeared as expected. That split between selection and focus is more than a cosmetic annoyance: it makes it harder to tell which item an interaction applies to, particularly when scanning a list of log entries.

Selection and focus are different states

For interface work, this distinction matters. Selection records which item a user has chosen; focus indicates which control or item currently receives keyboard interaction. In many lists, clicking a row updates both states together. When they diverge, the interface can show a partial or unexpected highlight, and keyboard navigation may appear disconnected from the user’s last action.

That mismatch is the practical issue LogUI 1.2 sets out to address. A user shouldn’t need to alternate between clicking and keyboard navigation just to make the chosen log entry appear fully selected. Bringing focus along with selection makes the result easier to read and the next interaction easier to predict. For anyone who regularly inspects logs, removing that repeated adjustment should make ordinary browsing less fussy.

A workaround, not a confirmed platform fix

The new version works around what the source describes as a bug in SwiftUI or macOS. It doesn’t establish which layer is responsible, and there’s no detail here about the implementation or whether the underlying behavior has changed in the platform itself. The reported fix is in LogUI: the application now handles the interaction differently so the selection and focus behave together.

The workaround draws on code written by Philip Savoulidis, whose publication made the change possible. That attribution is useful context: the fix depends on shared code, rather than a platform-level correction described in the release information. The source doesn’t explain the code’s specific mechanism, so it would be premature to assume it uses a particular SwiftUI API or changes how other applications behave.

That distinction also sets expectations. LogUI 1.2 may improve this specific experience without resolving similar behavior elsewhere in macOS or in other SwiftUI applications. Developers encountering the same symptom should treat this as a practical example to investigate, not proof that the workaround can be applied unchanged to every interface.

Who should install it

LogUI 1.2 build 91 is strongly recommended for people using Golden Gate, where the selection-and-focus problem affects LogUI 1.1. The source says it should continue to work on earlier macOS versions as well, though it doesn’t give a version-by-version compatibility list. Users on those systems can reasonably regard compatibility as intended, while recognizing that the available information doesn’t document testing across every release.

The update is available as a download, through the site’s Downloads section, and on LogUI’s product page. Before switching versions, users who depend on a particular workflow may want to check that their usual log browsing still behaves as expected. The source provides no separate notes about other changes, so the selection fix is the clear reason to upgrade.

The value is in removing friction

This is a modest release, but it addresses an interaction flaw at the point where users expect a click to work. The improvement won’t change what LogUI does with log data; it changes how clearly the interface represents the item the user has chosen. For a utility used to inspect entries, that clarity can matter more than a feature that adds another step or option.

What remains to watch is whether a later macOS or SwiftUI update changes the behavior enough to make the workaround unnecessary, or whether LogUI needs to keep handling the issue itself. For now, Golden Gate users on LogUI 1.1 have a straightforward reason to move to build 91: selecting an entry should no longer require Tab-and-Shift-Tab cleanup to show focus correctly.