I apologize, as I was on vacation and came back just now.
No, there has been no work so far.
I gathered all issues, showed why they happen and proposed solutions.
I can show you a transcript:
==================================================================================================
Tests made with DIVI from elegant themes (vanilla) and Toolset Types + Views, having the settings turned to "Toolset should load Bootstrap 3.0".
All tests are chronological from install > Visit HomePage > Visit Posts > Visit Pages > Visit Custom Posts.
1. Link Styles overwritten by Bootstrap (especially in the Menu Items):
Example:
.nav > li > a:hover, .nav > li > a:focus background-color: #eeeeee;
==> Should be changed in the Theme by adding a custom class to the href elements.
==> Or you need to add custom CSS to re-style the hover text color of DIVI, with an !important .
Not really the best solution.
2. All items added to HTML by DIVI that use the class "container" will be overwritten by the Bootstrap Classes for "container"
==> Should be changed in the Theme by adding a custom class to the containers, not using a vanilla name like "container"
==> This has the effect that if you look at your template with "This site is not using Bootstrap CSS" you will see exactly what DIVI outputs, when you activate "Toolset should load Bootstrap 3.0" things will get margins and paddings added by Bootstrap.
==> The main reason why DIVI should change this and not Toolset or Bootstrap is, they call this "Fullwidth" template.
But they add width: 80%;max-width: 1080px; while they do not pass a padding, which Bootstrap does, hence overwrites it.
3. Divi adds a padding to all "ul" items
which affects for example "wpv-pager-nav-links" since it'll now have a "1em" padding to the left.
4. Select fields are completely overwritten by Bootstrap, through our ".form-control" class.
This should be expected, as we provide a Bootstrap syntax. If you do not want to use that, but theme's, then it can be disabled in the View when inserting the Searches (Legacy code)
We could say the same for pagination elements using bootstrap.
These are the main issues seen, + the ones appearing when you begin to use WooCommerce, but that requires another round of tests.
Then there is a Bug, on Toolset side, where Fullwidth background not applied to Content Templates.
That is reported and has been solved here:
https://toolset.com/forums/topic/documentation-update-request-for-broken-fullwidth-layout-for-custom-post-types/#post-604460
Now, I tried to expedite a decision on these issues, because as you see, they are not solely on Toolset.
They require a careful decision, wether to hack or to not hack, wether to document it or not, etc.
The issue is on the Lead Developer's to do list, and when they reach this task I will get notified with the decisions.
I cannot suggest any thing else but to add Custom CSS to fix the issues, for now.
You may use the feedback form if you wish to enter in contact with the Management about this issue, I can assure that the issue is properly reported and debugged, but I cannot provide you the official decision and fix, as there is none yet.
I apologize the delay, and thank you for understanding.
