Steps to reproduce:
Go to any page on GitHub and compare vs Firefox for the expected UI changes brought on by the extension Refined GitHub
Orion and macOS:
Orion 0.99.109.1.3-beta, macOS 12.1
Image/Video:
This is just a couple examples, though applies to all expected UI changes on the homepage, project page, etc.
Hidden watcher/fork counts
Firefox:
Orion
File search button (lifesaver!)
Firefox:
Orion:
A full repo page
Firefox:
Orion:
I think this can be customized to your liking in the extension preferences, and not a bug with Orion.
cmd-shift-L -> Extensions 
Yep that's correct - however, they have no effect. For example,
is turned on, yet does not do anything
Facing the same issue.
I also see this error in the browser console:
SyntaxError: Unexpected identifier 'open'. Expected ')' to end an argument list.
Checking the source, it seems like it's failing to parse this line: https://github.com/refined-github/refined-github/blob/aba5560dbf9c3a94607e654e9469a3df6084f116/source/refined-github.css#L19
Perhaps the ` character is causing parsing issues?
2 more errors while configuring this:
Unhandled Promise Rejection: TypeError: null is not an object (evaluating 'response.headers.get("X-OAuth-Scopes").split')Source (in case it helps): https://github.com/refined-github/refined-github/blob/de1287f62fd27d42a97d7d5615903510d4954755/source/options.tsx#L62
Failed to load resource: The operation couldn’t be completed. (Orion.SchemeHandlerError error 2.)Checking the network tab, it seems to be trying to access chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/favicon.ico, and I am assuming Orion is failing to parse chrome-extension as a valid scheme?
I took a bit of a look into this, and it seems that Refined is trying to access the X-OAuth-Scopes header. That is included in the Access-Control-Expose-Headers header object (so it should be accessible), but looking at the actually available headers in the Response's Header object, only a small subset are shown. The header list in the network tab does include the scopes header, but it's lowercased, as x-oauth-scopes.
Available Headers within the console:
["access-control-allow-origin", "access-control-expose-headers", "cache-control", "content-encoding", "content-security-policy", "content-type", "date", "etag", "referrer-policy", "vary", "x-content-type-options", "x-frame-options", "x-xss-protection"]
This is the value of Access-Control-Expose-Headers in the network tab:
ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset.
phildenhoff Is there anything actionable for us?
Yes, I would do a quick check to make sure that Orion is correctly applying Access-Control-Expose-Headers in extensions without case-sensitivity — AFAIK, if the header is in that list, it should be available to requester (whatever called fetch()).
In this case, Access-Control-Expose-Headers includes a header (x-oauth-scopes) that isn't available to the requester. It does exist in the browser network tab so it should be available. It could be a webkit bug, but apparently Safari supports Access-Control-Expose-Headers.
Also, extension configuration page shows an error accessing X-OAuth-Scopes header when a valid token is introduced.
It seems Orion has some problem accesing this header.
But header is actually in the response of the request as is shown in the Network tab of the inspector.
gotcha, done. link for future reference and others that might end up in this thread. https://orionfeedback.org/d/3851-refined-github-is-not-able-to-verify-token
