Skip to content

Commit

Permalink
Remove logging of invalid selector matching
Browse files Browse the repository at this point in the history
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
  • Loading branch information
FremyCompany committed Dec 6, 2020
1 parent 4cc1aae commit d40c91b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/core/css-cascade.js
Original file line number Diff line number Diff line change
Expand Up @@ -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]); }
Expand Down

0 comments on commit d40c91b

Please sign in to comment.