well the status is a bit complex, so I try to give a short summary.Frontend module files
The optional Add-on files "frontend.css" and "frontend.js" are automatically loaded by WB, if the "register_frontend_m
odfiles" function is invoked from the index.php of the frontend template.
Note: This does not work in all module files, it just works in WB controlled files such as "view.php". So if you have a "save_my_settings.ph
p" which does something in the frontend part of your Add-on, the frontend files will not automatically be included.Backend module files
The optional Add-on files "backend.css" and "backend.js" are automatically loaded by WB since WB 2.7.
Note: This does not work in all module files, it just works in WB controlled files such as "include.php", "modify.php".jquery-min.js
Automatically loaded in backend pages, which includes the theme file "footer.htt" (e.g. /template/xxx_theme/templates/footer.htt). The JS lib is included to the end of the body not in the head.
Note: while "jquery-min.js" is loaded in all themes, "jquery-ui-min.js" is not loaded automatically by all themes.EditArea
Automatically included in the head secton of all backend pages (2.8.1). Loading mechanism was changed some times from 2.8 RC1 to 2.8.1. Latest load mechanism is to include this lib via /template/xxx_theme/templates/header.httNon WB controlled Add-on files
In non WB controlled Add-on files (e.g. files which take values from AJAX, Forms etc.) and save them to DB etc, the developer needs to take care that JS or CSS files are included. On possbile way of including files to non WB controlled Add-on files is shown in the AFE "action_handler.php" file (function myAdminWrapper).
P.S.: The summary is by no means exhaustive. I just wanted to highlight some of the aspects. Files like the "frontend_body.js" are not even mentioned above. Maybe some aspects will be documented with the updated WB help site