Which Eclipse preference forces third-party plug-in views into the active high-contrast theme?

The Eclipse IDE exposes theming controls through Window > Preferences > General > Appearance, including Theme and Colors and Fonts entries. Standard workbench parts and SWT/JFace widgets generally track those settings, but custom-drawn third-party plug-in controls may retain hard-coded colors or ignore theme switches entirely. Because Eclipse 4.x e4 CSS theming differs from 3.x, and because SWT behavior varies across the Win32, GTK, and Cocoa ports, it is unclear whether any single platform preference can force third-party plug-in views and wizards into the active high-contrast or system-dark theme.

Forced remapping of third-party plug-ins is not established as guaranteed Eclipse platform behavior, and exact preference or theme identifiers can change between releases. Verification with representative plug-ins on the target release and OS port is required before assuming compliance, leaving the ownership of remapping unresolved.

Which documented preference, if any, forces third-party plug-in UIs into the active high-contrast or dark theme? Does ownership of remapping rest with the Eclipse platform or with individual plug-in vendors? How should teams verify contrast and focus indicators for custom plug-in widgets across Windows, Linux/GTK, and macOS?