I have a asp.net label control . The label is inside the control Panel
and the page also has a master page. The label ID is lbErrorList.
The label gets rendered as
"ctl00_ctl00_SubApp1_SubContent_lbErrorList"
The page also contains many textbox which needs to be populated by
user. I am trying to
Here is the solution..
1. Take 2 DIV containers name them (for example) as OuterDIV and
InnerDIV. InnderDIV inside OuterDIV.
2. Assign class OuterDivClass to OuterDIV .
3. Assign class InnerDivClass to InnerDIV.
Observe that when OuterDIV gets displayed it occupies complete screen
due to height
I've also been among those clamoring for an optimized $.live method
and have a offered similar hack around in the past (via Paul Irish's
Anti-Patterns). Last night on the flight to jsconf, I hacked up a more
formal patch which puts optimized live and die methods into the jQuery
root and aliases th
I wonder why there would be an $.live with document as the only
interesting context.
Something like
$(document).zombi(selector, type, ...)
would be more flexible (I know, "zombi" is not nice, but I have no
inspirations about a more suitable name).
To avoid to repeat selector on multiple bindi
I little while ago I had a situation where I thought it would be
useful to bind jQuery events to custom JavaScript objects. I didn't
think it should work, as I thought you could only select DOM nodes.
But as you probably know - that's not true. You can select objects too
(boring details here...
ht
How about $("#something").delegate(".thing","click", func).
It almost makes too much sense :).
On Nov 5, 6:31 pm, Robert Katić wrote:
> I wonder why there would be an $.live with document as the only
> interesting context.
>
> Something like
>
> $(document).zombi(selector, type, ...)
>
> would
The fix function is rather expensive for things like mousemove and
mouseover. Can we make it possible that events won't be fixed for
certain events?
If you like this idea, I'll submit a patch.
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" gro
Meyer, "delegate" was my first candidate too but I was worry that it
was overused :). Seams that I was wrong. Will update it with
"delegate" ASAP.
--Robert
On 6. stu. 2009., at 02:42, Justin Meyer wrote:
> How about $("#something").delegate(".thing","click", func).
>
> It almost makes too m
The only case where that sort-of makes sense is for custom events. I
mean, there's not much point in not-fixing the event object for some
events - might as well do it for no events then.
...unless there's something else that you were considering?
--John
On Fri, Nov 6, 2009 at 2:43 AM, Justin M
I don't think that the method name is at question here, but rather the
unnecessary performance cost of querying a selector before DOMReady
(or even after), ie. $('#anything'), when it is not needed for the
event delegation pattern. The .live method uses only the .selector
property of the jQuery ins
> Also, @robert, my solution supports the following notation, similar to
> yours but using the familiar jQuery syntax (before/after DOMReady):
> $.live("#mySelector", "click", fn1)
> .live("#mySelector", "mouseover", fn2)
> ...;
I understand the logic behind you wanting a $.live method (for the
It was unintentional - way back in the day - but we've come to embrace
it. Expect those aforementioned methods (bind/unbind and data) to
continue to work on plain JavaScript object.
--John
On Fri, Nov 6, 2009 at 1:31 AM, Mr Speaker wrote:
> I little while ago I had a situation where I thought
jQuery JavaScript Library v1.3.2
jQuery validation plug-in 1.5.5
I'm working on a form with a bunch of fields with MaxLength
validators.
When a field with contents are erased the jquery.validate element
function kicks in, sees one validator (for max length), which, when
evaluated returns "dependen
What about something like this:
$.live = function(selector, type, callback) {
$.fn.live.call({ selector: selector }, type, callback);
}
On Thu, Nov 5, 2009 at 7:13 AM, xwisdom wrote:
> Hi John,
>
> Thanks for the quick feedback
>
> IMO, I think it would be handy to have somethin
$("#someRootTable").delegate("td.foo", "click", function(e){
// Your code goes here.
});
Would be easer and safer because the event will be handlet only by
"td.foo" elements inside "#someRootTable".
--Robert
On 6. stu. 2009., at 04:56, John Resig wrote:
> $("#someRootTable").click(functi
If you want to limit, just do this (using the nightlies):
$("#someRootTable").click(function(e){
$(e.target).closest("td.foo", this).each(function(){
// Your code goes here.
});
});
Still pretty simple and requires no additional functionality. I may
just write this up as an example and a
I suppose you will need an "return false;" too at the end of the
handler...
--Robert
On 6. stu. 2009., at 05:29, John Resig wrote:
> If you want to limit, just do this (using the nightlies):
>
> $("#someRootTable").click(function(e){
> $(e.target).closest("td.foo", this).each(function(){
>
No you will not. My Mistake
--Robert
On 6. stu. 2009., at 05:29, John Resig wrote:
> If you want to limit, just do this (using the nightlies):
>
> $("#someRootTable").click(function(e){
> $(e.target).closest("td.foo", this).each(function(){
> // Your code goes here.
> });
> });
>
> Still
I searched around for this, but couldn't find any mention of it...
which seems a bit spooky, but I'll post it anyway. In this code:
$("#complete").ajaxComplete( function(){ $(this).text("complete"); });
$("#start")
.ajaxStart(function(){$(this).text("start")})
.ajaxStop(function(){
Regarding improving live(), I would note two things about liveHandler:
1. Calling closest, context argument still is not used.
I was unable to find the proper ticket. Would I open one?
2. Storing "how much a parent is close to an element" with data API is
an big overhead. An jQuery.lastCloser or
20 matches
Mail list logo
