Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Wait, never mind, I think - it looks like part 2 in my original comment is fixed, so it's only half still problematic.
As a note, this defect remains in 12.0.1. It's due to the conditionals in
com.ibm.xsp.theme.bootstrap.resources.Resources
.The bug here comes from two layered problems:
1) The general choice to base renderer behavior on the specific string name of the root theme in the "extends" chain
2) A bug in the `Resources` utility class that uses the current theme name as opposed to actually finding the root theme
This can also potentially (based on threading) manifest in an app directly using "Bootstrap4" (or a theme named starting with "Bootstrap4") if another app on the server extends any HCL-provided Bootstrap theme but uses a theme that doesn't start with "Bootstrap4". Or vice versa, since the trouble is the same.