Closed (won't fix)
Project:
Bootstrap
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Oct 2013 at 23:14 UTC
Updated:
14 Mar 2015 at 18:23 UTC
Jump to comment: Most recent
Comments
Comment #1
markhalliwellI know that this is the first time I have said anything on this issue, but I would like to preface this with: I have actually spent a great deal of time thinking about this particular issue along with many others regarding CDN support (related issues).
What this issue really boils down to is manageability. Not only from a site building standpoint, but also from a maintainer's standpoint of this project. Introducing an entirely separate UI to handle one or the other, or both, and the logistic it will take to make sure there is no compatibility issues (i.e. version differences) is going to be a nightmare; believe me, I tried.
I would much rather take the KISS approach here and say: 1) If you're plan on using the CDN, then use it or 2) If you need to customize, then do everything locally and then put that behind a custom CDN if one is still needed.
Comment #2
markhalliwellSo while I was coding #2450757: Provide a more robust CDN solution I designed it so you could actually set the provider to "custom" and then just provide only the JS files you want loaded from a specific CDN. This is probably the closest I'll be able to get to your original request, but it should work rather well... in theory :)