Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8668301
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T18:10:47+00:00 2026-06-12T18:10:47+00:00

i have noticed that this line $(‘#opp-tabs input[type=text]:not(#newActionText), #opp-tabs textarea’).live(‘keyup’, function() { onFormChanged(); });

  • 0

i have noticed that this line

    $('#opp-tabs input[type=text]:not(#newActionText), #opp-tabs textarea').live('keyup', function() {
        onFormChanged();
    });

runs extremly slow in IE8, it works fine in firefox and chrom but not in IE, it to be honest it is cos of word ‘not’, how can it define this different to run in normall speed in IE ?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T18:10:49+00:00Added an answer on June 12, 2026 at 6:10 pm

    You really should make sure that selectors are as lightweight as possible, especially if used in .live() methods. What happens there is, that the event actually gets bound to the document.body and it needs to check there whether or not a given event matches your original selector string. That process can be pretty expensive and in your case it also needs to invoke Sizzle**, which makes it even slower.

    Best case solution, use .on() or .delegate() to limit the necesarry DOM bubbling. That means, you don’t bind the event handler to the body, but to the closest shared parent node, which increases overall performance. Secondly, more important, improve that selector!

    Use class names or whatnot to query for the nodes you require, actually it can’t be much worse than the current state.

    To optimize the current form, try it like so:

    $('#opp-tabs input:text, #opp-tabs textarea').not('#newActionText').on('keyup', 'closest shared parent selector', function() {});
    

    Reference: .delegate(), .on()

    ** Sizzle is jQuery’s javascript css-selector engine

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This question may not directly relate to programming. I have noticed that the technology
I have noticed a number of kernel sources that look like this (found randomly
I noticed that some stylesheets have something like this: body { font-size: 62.5%/1.2em; }
I have never come across this issue but most recently I noticed that a
I have noticed that deleted branches in svn is not preserved in git. I
From this previously asked question , I have noticed that when I move a
I noticed that this line... OLDPWD /webroot/shareddev/xdebug/xdebug-2.1.1/xdebug-2.1.1 ...appeared or was modified after I compiled
We have noticed that component publishing takes a long time. The component we are
I have noticed that if you add a unobtrusive link in a refreshable partial
I have noticed that ie tends to put the thread for a tab to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.