The wpv-pagination.css file is use for view pagination, and it is registered in the Views's plugin file \wp-views\embedded\inc\wpv.class.php, line 197:
// Datepicker script bundled with WordPress
wp_enqueue_script( 'jquery-ui-datepicker' );
In my old code this was removed by:
wp_deregister_script( 'jquery-ui-datepicker' );
This is still working but it's giving errors. I tried wp_dequeue_style instead, but that is not removing anything in my sourcecode. The deregister removes this (but gives errors):
This file comes from Types plugin, but I can not duplicate same problem in my localhost with the latest version of Types, there isn't such a file loaded in the front-end, I checked the source codes of Types plugin, it is registered in file \types\embedded\common\toolset-forms\classes\class.date.scripts.php, line 97:
And for the question: why are these CSS/JS included when these featured are not used?
I think some Views/Types shortcodes run in the wordpress content, the JS/CSS file load in the wordpress header, earlier than the content, it is unknown that if there are pagination or datepicker feature in shortcode, so it loads these CSS/JS in front-end in case there are pagination or datepicker. I think we can put it our to-do list as a feature request.
Yes. please add it as feature request, i will check the code again with latest version, I don't use latest version yet because it breaks something else I build with Toolset. Thank for your help sofar i will follow up soon when I tested it with recent version.