-
Notifications
You must be signed in to change notification settings - Fork 788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hcm.paycor.com: breakage #26528
Comments
@dluong06 We can't investigate without an account.
or tell us if you want share your account |
Also, since you opened dev tools, can you share reported errors in the console? It says 9 errors in your screenshot. Something else to try is to set default filtering mode to Optimal, this enables redirection and may help with lowering likelihood of breakage. |
@MasterKia I was able to reproduce the issue with UBO on firefox and here is all the blocked and modified. Obviously wasn't able to use the question mark button as its being blocked. Logger output
@gorhill Reproduced that exact scenario in Chrome in UBOL as show in screenshot. Uploaded as a log file from dev tools since it won't play nice here in the code markdown. |
@dluong06 Try these filters in "My filters" and see which one works: @@||googletagmanager.com/gtm.js^$domain=hcm.paycor.com
@@||hcm.paycor.com/authentication/Content/Scripts/newrelic.js^
|
Prerequisites
Complete
filtering mode.URL address of the web page
https://hcm.paycor.com/
Category
breakage
Description
Ublock lite under basic all the way to complete seems to blocking a button/menu incorrectly
(EDIT: I should have added that the image is in reference to it working with ublock fully disabled for the site just so that I can inspect the site button/menu properly. )
Other extensions used
Happening on at least 2 systems utilizing ublock lite with no extensions at all besides ublock lite.
My system has lastpass, keeper, scribe, paypal honey, betterttv and also has the same issue under the defined conditions.
Screenshot(s)
Screenshot(s)
Configuration
The text was updated successfully, but these errors were encountered: