I read the blog post @mibalan did on using QUnit and Browerscope to create the CSS regions support matrix.
Long story short, I played around with the code using your test-key to debug UI, thought I wasn't submitting any data... But apparently I did submit some invalid keys :(
I don't think there's much I can do - but, to say sorry. I can't retract results from browserscope.
I'm quite embarrassed, so again I'm terribly sorry.
A quick workaround would be to add the following line to utilities/css-regions-support-matrix/assets/js/results.js between line 141 and 142 (in the createTableRows function).
Even better of course would be to only read keys that you have unit tests for, but that would require a wrapper for defining the tests and saving test name onload. Nevertheless, it's probably impossible to make a tamper-free crowd sourcing solution, so that's probably overkill.
Again, I'm terribly sorry... And hope this fix works for you, if not let me know...
I read the blog post @mibalan did on using QUnit and Browerscope to create the CSS regions support matrix.
Long story short, I played around with the code using your test-key to debug UI, thought I wasn't submitting any data... But apparently I did submit some invalid keys :(
I don't think there's much I can do - but, to say sorry. I can't retract results from browserscope. I'm quite embarrassed, so again I'm terribly sorry.
A quick workaround would be to add the following line to
utilities/css-regions-support-matrix/assets/js/results.js
between line 141 and 142 (in thecreateTableRows
function).Even better of course would be to only read keys that you have unit tests for, but that would require a wrapper for defining the tests and saving test name onload. Nevertheless, it's probably impossible to make a tamper-free crowd sourcing solution, so that's probably overkill.
Again, I'm terribly sorry... And hope this fix works for you, if not let me know...