Plugin Author
Meitar
(@meitar)
Welcome to the Web. ¯\_(ツ)_/¯ This isn’t something I’m going to bother addressing. My advice is to not care.
Thank you for the quick response. shrug. I can probably live with it, though the prevalence of MS browsers – which I only use for testing purposes – may be an issue. I will test the matter further to see what sense I can make of it all.
Overall let me say that I am really super impressed with the speed of return on searches once the page is loaded. I needed to test on a reasonable size data set, similar to what we will use live, as I could have impressed with a dataset of 25 items, but that may have been smoke and mirrors.
Travel well my friend, once in place there should be some coffee money for you.
Just so you know, I discovered these variations in rendering of the tables. I find this a little frustrating as I thought the days of browser variant behavior were supposed to be behind us.
Widths Firefox Chrome MSEdge
Col1 66 64 65
Col2 62 60 61
Col3 49 48 48
Col4 58 56 57
Col5 46 47 48
Col6 42 42 43
Col7 52 53 55
Col8 55 55 56
Col9 42 42 42
Col10 72 69 68
Total 544 536 543
Table 924 916 923
All three browsers here have left 380 for space/padding/margins etc, so they are consistent there.
If you use the column visibility tool to turn off all columns and then turn them all back on you get an altogether different result.
