**Bulk edit**

We are now past M-53 FF. Since you still haven't transitioned to a review state, we are assuming that you are not planning to launch in M-53. As such, we're updating the MStone to M-54.

If you still intend to launch in M-53, feel free to change this back, but *please begin your xfnl reviews now*!

Thanks for your help with ensuring a smooth process.

I will launch only supporting -webkit-user-select:all in M53 and remains will be in M54.

We shipped 'all' and unprefixing.
b/481985 will be fixed in another milestone.

Friends,

Working with jQuery DataTables (v1.10.15 with Select Extension v1.2.2) running under the current version of Chrome (59.0.3071.86 64-bit), I notice the following issue:

On tables containing many rows (10K +), setting the 'user-select: none' style on the <table> element results in noticeable processing delays whenever the user left-clicks (to select) or right-clicks (to display the pop-up menu) on a table row.  Removing the style from the <table> element and applying it to each <tr> element eliminates the processing delay.

Please note: Applying 'user-select: none' to the table element in IE 11 or Firefox works as expected - no processing delay on left- or right-clicks.  

Full disclosure: I use the following CSS class to achieve some measure of 'browser independence':

.disable-selection {
      -webkit-touch-callout: none; /* Disable Android and iOS callouts*/
      -webkit-user-select: none; /* Chrome, Safari, and Opera */
      -khtml-user-select: none; /* Konqueror - Support for Safari 2.0? */ 
      -moz-user-select: none; /* Firefox */
      -ms-user-select: none; /* Internet Explorer/Edge */
      user-select: none;    /* Standard Property */
}

Since the standard says 'user-select' can be applied to 'all' elements, am I correct in thinking Chrome should fully support its use on the <table> element? 

Many thanks in advance for your help!!

Best,

Brian Cummings
Software Engineer, Senior
CUAHSI

1. Applying user-select:none on a top element having much children and clicking on it 
 can cause performance issue because Chrome search 'clickable' element traversing the
 tree.
If it is significant problem, please submit as new issue (maybe titled "clicking on user-select:none is slow"?) since this is standerdize tracking issue.

2. Yes, we support user-select:all on table element. If you find some behavior strange
 or differ from other browsers, we're happy with your feedback:)