with newer versions of typescript (>v2 i believe): npm install -D @types/bootstrap Edit: As hughjdavey said in his comment, you also need the following import lines: import * as bootstrap from “bootstrap”; import * as $ from ‘jquery’;
The collapse events are handled differently in Bootstrap 3. Now it would be something like: $(‘#collapseDiv’).on(‘shown.bs.collapse’, function () { $(“.glyphicon”).removeClass(“glyphicon-folder-close”).addClass(“glyphicon-folder-open”); }); $(‘#collapseDiv’).on(‘hidden.bs.collapse’, function () { $(“.glyphicon”).removeClass(“glyphicon-folder-open”).addClass(“glyphicon-folder-close”); }); Demo: http://www.bootply.com/73101
Always use parseInt with a radix (base) as the second parameter, or you will get unexpected results: var number = parseInt($(this).find(‘.number’).text(), 10); A popular variation however is to use + as a unitary operator. This will always convert with base 10 and never throw an error, just return zero NaN which can be tested with … Read more
I had the same problem. In v4 all suggestions above did not work for me, but this did: tinymce.remove(“div.editable”); … regenerated HTML dynamicaly … tinymce.init(…); I use inline editor: tinymce.init({ selector: “div.editable”, inline: true, plugins: [ “advlist autolink lists link image charmap print preview anchor”, “searchreplace visualblocks code fullscreen”, “insertdatetime media table contextmenu paste” ], … Read more
Update: This issue has been fixed in the latest NuGet package. I’ve posted another answer to reflect this. https://stackoverflow.com/a/15539422/714309 In jquery.unobtrusive-ajax.js, find and replace these four lines: $(“a[data-ajax=true]”).live(“click”, function (evt) { $(document).on(“click”, “a[data-ajax=true]”, function (evt) { $(“form[data-ajax=true] input[type=image]”).live(“click”, function (evt) { $(document).on(“click”, “form[data-ajax=true] input[type=image]”, function (evt) { $(“form[data-ajax=true] :submit”).live(“click”, function (evt) { $(document).on(“click”, “form[data-ajax=true] :submit”, … Read more
Would this work? http://darcyclarke.me/development/detect-attribute-changes-with-jquery/ $.fn.watch = function(props, callback, timeout){ if(!timeout) timeout = 10; return this.each(function(){ var el = $(this), func = function(){ __check.call(this, el) }, data = { props: props.split(“,”), func: callback, vals: [] }; $.each(data.props, function(i) { data.vals[i] = el.css(data.props[i]); }); el.data(data); if (typeof (this.onpropertychange) == “object”){ el.bind(“propertychange”, callback); } else if ($.browser.mozilla){ el.bind(“DOMAttrModified”, … Read more
AFAIK you cannot make the red thingies go away, when returning error status-codes (4xx, 5xx). They are used by the browser to indicate that something might have not gone as expected. Still these are mere decorations, since 4xx and 5xx status codes are perfectly valid, so I don’t see a reason for you wanting to … Read more
You can call infowindow.setContent at any point after the info window has been shown. So you could initially set your info window content with a spinner, make the AJAX call (from the event handler) and then call infowindow.setContent again from the AJAX response with the appropriate data.
The best I think is using Comet. In Comet-style applications, the server can essentially push data to the client (instead of the client request data from the server again and again.). The client needs to only connect to server once. and then server will keep pushing data back to client. From Wikipedia: Comet is a … Read more
Just been looking at this myself. jQuery does return things in document order as per the following article: http://docs.jquery.com/Release:jQuery_1.3.2 So, if you select some ids as such: $(“#id1, #id2, #id3”) Then they will be returned in the order they appear in the DOM, not necessarily in the order they are given. Its certainly worth being … Read more