Does Selenium 4 provide native locator context in StaleElementReferenceException logs?

When a StaleElementReferenceException occurs during a test run in Selenium 4, the default log output typically includes the exception stack trace and a general error message. However, the logs do not automatically capture the specific locator strategy or the element identifier that triggered the staleness.

While WebDriverListener allows for the manual registration of custom logging to capture the element's last known location and the action being performed, this requires additional boilerplate code and is not enabled by default. This creates a gap in failure diagnosis when analyzing logs from large-scale test suites where custom listeners may not be implemented.

Which configuration or native logging property in Selenium 4 allows for the inclusion of the element locator within the standard exception log without implementing a custom WebDriverListener? Does the shift to SLF4J-based logging provide a mechanism to increase the granularity of these specific exception details?