Skip to main content

Using Visual Studio Intellisense for building jQuery selector strings

Image
By User


This is a minor issue, but one I find myself running into:



When I am using jQuery in Visual Studio 2010, I find myself frequently typing: 





$(#S


using Intellisense to find the SomeID object ID: 





$(#SomeID).click( function() { etc.. })


then going back and adding quotes: 





$('#SomeID').click( function() { etc.. })


I find it annoying that if I add the quote first, Visual Studio goes into string mode and I lose Intellisense for finding the object's ID or class.



Am I doing it wrong?


Source: Tips4all, CCNA FINAL EXAM
Labels:

Comments

  1. UserMay 13, 2012 at 8:32 AM

    Unfortunately Intellisense for jquery on VS2010 is far from perfect,
    It has various problems like the one you mentioned above and it is knowN to cause performance issues within VS itself, for me typing at times was unbearably slow.
    You could always create some snippets to speed up your worklow, but unfortunately that wont actually fix your problem with the intellisense. Lets hope they release a fix for this in their first service pack.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月１０日ごろ＝韓国

By Unknown
Post a Comment
Read more

div not scrolling properly with slimScroll plugin

By User
I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?
1 comment
Read more

Why does this javascript based printing cause Safari to refresh the page?

By User
The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
5 comments
Read more