From d40c91b388b490cf29fb92ab307f67e5c5015c6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20REMY?= Date: Sun, 6 Dec 2020 15:51:27 +0100 Subject: [PATCH] Remove logging of invalid selector matching Selectors which are invalid are often caused by vendor prefixes, and it is not useful to log these. An author can look into regular css parsing of the page to look at thse --- src/core/css-cascade.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/core/css-cascade.js b/src/core/css-cascade.js index e40f154..c842bdb 100644 --- a/src/core/css-cascade.js +++ b/src/core/css-cascade.js @@ -137,7 +137,7 @@ module.exports = (function(window, document) { "use strict"; else if(element.mozMatchesSelector) isMatching=element.mozMatchesSelector(selector) else if(element.webkitMatchesSelector) isMatching=element.webkitMatchesSelector(selector) else { throw new Error("no element.matches?") } - } catch(ex) { debugger; setImmediate(function() { throw ex; }) } + } catch(ex) { /*debugger; setImmediate(function() { throw ex; })*/ } // if yes, add it to the list of matched selectors if(isMatching) { results.push(subrules[sr]); }