Skip to main content
Code Review

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Your jQuery could be somewhat more efficient if you minimize $(...) element look-ups by storing them as variables or chaining them.

Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

Check out this set of jsPerf tests from this StackOverflow answer this StackOverflow answer.

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $this = $(this),
 $thisVal = $this.val();
// ...

Your jQuery could be somewhat more efficient if you minimize $(...) element look-ups by storing them as variables or chaining them.

Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

Check out this set of jsPerf tests from this StackOverflow answer.

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $this = $(this),
 $thisVal = $this.val();
// ...

Your jQuery could be somewhat more efficient if you minimize $(...) element look-ups by storing them as variables or chaining them.

Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

Check out this set of jsPerf tests from this StackOverflow answer.

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $this = $(this),
 $thisVal = $this.val();
// ...
added 192 characters in body
Source Link

Your jQuery could be somewhat more efficient, if you save reusedminimize $(...) chunks in their ownelement look-ups by storing them as variables or chaining them. Also

Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

Check out this set of jsPerf tests from this StackOverflow answer .

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $this = $(this),
 $thisVal = $this.val();
// ...

Your jQuery could be somewhat more efficient, if you save reused $(...) chunks in their own variables. Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $this = $(this),
 $thisVal = $this.val();
// ...

Your jQuery could be somewhat more efficient if you minimize $(...) element look-ups by storing them as variables or chaining them.

Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

Check out this set of jsPerf tests from this StackOverflow answer .

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $this = $(this),
 $thisVal = $this.val();
// ...
fixed code typo
Source Link

Your jQuery could be somewhat more efficient, if you save reused $(...) chunks in their own variables. Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $thisVal$this = $(this),
 $thisVal = $this.val();
// ...

Your jQuery could be somewhat more efficient, if you save reused $(...) chunks in their own variables. Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $thisVal = $(this),
 $thisVal = $this.val();
// ...

Your jQuery could be somewhat more efficient, if you save reused $(...) chunks in their own variables. Also, I think you will see some benefit to replacing some jQuery constructs with their pure JS alternatives ($.each -> for, etc..)

<script>
var fullcelllist = $(),
 lastVal ="",
 $celllistOption = $("#celllist option");
// ...
$("#filtercell").keyup(function() {
 var $this = $(this),
 $thisVal = $this.val();
// ...
Source Link
Loading
default

AltStyle によって変換されたページ (->オリジナル) /