News for hackers. Stuff that matters.
Re:An update to UBlock Origin was rejected by the Chrome Web... by neoeldex on Thursday October 29, 2015 @09:52AM (#10470941)
Just switched over, but I'm wondering what you mean by blocking DOM? are you using lynx? CSS visited links are not able to be checked using javascript, so why are you blocking this?
Re:An update to UBlock Origin was rejected by the Chrome Web... by bcg1 on Thursday October 29, 2015 @10:06AM (#10471043)
Are you sure?

Could someone add some invisible 'before: content()' (or however that works in CSS) inside of an a:visited rule, and then check the DOM via Javascript to see if that content is there?

I haven't tried this, but it seems like it should work unless there is something specifically blocking that

Re:An update to UBlock Origin was rejected by the Chrome Web... by kiiski on Thursday October 29, 2015 @10:52AM (#10471431)
That doesn't work. Browsers are smart enough to limit what you can do with :visited.

See for example: https://developer.mozilla.org/en-US/docs/Web/CSS/Privacy_and...

Re:An update to UBlock Origin was rejected by the Chrome Web... by bcg1 on Thursday October 29, 2015 @03:05PM (#10473447)
Good to know, thanks