Summary of Changes

The ResultType*Aware traits (Array, Float, Integer, Numeric, Object, String) carried a $resultIsFalseable flag, tagged @deprecated 4.3 will be removed in 7.0, that let an event class accept false as a result of that type. This removes the flag and the branch in typeCheckResult() that honoured it. $resultIsNullable stays.

No core event class ever set the flag to true, so core behaviour does not change: a false result on one of these events already raised the "only accepts ... results" InvalidArgumentException. Extension event classes that set it to true now get that exception for false results, which the deprecation notice announced: use null with $resultIsNullable, or throw.

Testing Instructions

1. Code review. grep -rn resultIsFalseable libraries administrator components plugins finds nothing.
2. Apply the patch. Site: open an article with content plugins active (page break, vote, email cloak); titles and content render (onContentAfterTitle, onContentBeforeDisplay, onContentAfterDisplay use the Array trait).
3. Administrator: the Home Dashboard shows the quick icons and the sample data module (onGetIcons, onSampledataGetOverview).
4. Administrator: Users > Multi-factor Authentication for a user lists the methods and opens the setup of one (MultiFactor events use the Object and Array traits).
5. Site: the login module shows the passkey button when the WebAuthn plugin is enabled (onUserLoginButtons).
6. Turn debug on and check no PHP notice, warning or deprecation appears during steps 2 to 5.

Actual result BEFORE applying this Pull Request

Everything works. The flag exists, nothing in core sets it.

Expected result AFTER applying this Pull Request

Everything works the same. The flag and its branch are gone.

Link to documentations

• No documentation changes for guide.joomla.org needed
• Pull Request link for manual.joomla.org: joomla/Manual#718