All of these points sounds very reasonable to me. Making these changes
to the markup will require some changes to our tests (since some IDs
are referenced by name) but this is a change that would be acceptable
to make.
Looking forward to your patch!
--John
On Thu, Jul 2, 2009 at 1:55 PM, brav
I'm building out a set of qUnit tests at work. So far all is going
well, and the tests have proven valuable. However, I'm having some
integration issues with the way qUnit does its reporting and layout.
The biggest isses I see are:
- The testsuite.css file makes some rather intrusive declarations
var errorFields = $('li:has(span[controltovalidate]) input:visible');
doesn't work for you?
On Jul 1, 9:41 am, Sean wrote:
> This works
> var errorFields = $('li:has(span[controltovalidate]) input');
>
> but I need to only select those that are visible
>
> style="visibility:visible"
--~--~
Quick test put together with the object check: http://jsbin.com/ifuti/edit
- works in IE8.
On Jul 1, 2:39 pm, Dave Methvin wrote:
> Definitely requires some extra work and testing to get right on all
> browsers.
>
> http://stackoverflow.com/questions/538745/how-to-tell-if-a-script-tag...
>
> May
You can call jQuery.ready() to fire all the queued functions.
On Jun 30, 9:49 pm, Steven Parkes wrote:
> I dynamically load jquery into my page and the change that happened at/
> round Ticket 2614 (http://dev.jquery.com/ticket/2614) / rev 5970 (or,
> in other words, between 1.2.6 and 1.3.2) had,
Hi,
Does jQuery or a plugin provide number and date parsing for the
current culture?
There is support in the Microsoft.Ajax library, but I was a bit
reluctant to add this to my project as its large and has a lot of
overlap with jQuery.
Ta, Ant
--~--~-~--~~~---~--~--
