Changed selectiblity behavior
I can no longer 'Select all' of a simple html table displayed in the browser. The header lines won't select no matter what I try. The browser only allows the body lines to be selected, and subsequently copyied.
Source:
Location | Heat Setpoints | Cool Setpoints | ||||||
---|---|---|---|---|---|---|---|---|
Zone | BldgFlrRm | Thermostat | Day | Night | Weekend | Day | Night | Weekend |
Lobby | First Floor | Lobby Down | 70 | 64 | 60 | 73 | 84 | 84 |
Lobby | Second Floor | Lobby Up | 69 | 64 | 60 | 72 | 84 | 84 |
Chosen solution
Tablesorter disables table header text selection by default:
cancelSelection
Boolean true
Indicates if tablesorter should disable selection of text in the table header (TH). Makes header behave more like a button.
All Replies (4)
In partial response to my own request, the Firefox browser is now sensitive to the <thead> tag that is used by the jquery code tablesorter.js to distinguish header entries from detail entries in a sortable table. My table includes <thead> </thead> <tbody> </tbody> tags. Until recent this caused no selection issues. Now it does. Can that be fixed?
Chosen Solution
Tablesorter disables table header text selection by default:
cancelSelection
Boolean true
Indicates if tablesorter should disable selection of text in the table header (TH). Makes header behave more like a button.
If you are the author of the website, you can adjust your code using the tip mentioned by zeroknight.
If you are an end user trying to work around this type of rule on a website you don't control, you could potentiall use an add-on or custom style rule. See:
https://www.reddit.com/r/firefox/comments/y76ndq/extension_which_will_let_me_selecthighlight_text/
Hi zeroknight and jscher2000, Yes, it's my website, so I have control of the code. Thank you so very much for your help. Never guessed it would be a configuration option. Just as an FYI, it seems to have changed behavior on Firefox only recently as I've used the same code for a long time. The same code still works the same on Chrome, FWIW. Regardless, it now works again on Firefox with a very minor tweak. Cheers, Fred