The issue has been closed
<!--
Thanks for reporting a bug! ā°
1. Make sure the bug is caused by Refined GitHub. Try disabling the extension first.
2. Include a full URL where the bug appears.
3. Include a screenshot/gif
Issues without a URL/screenshot will be closed
-->
GH updated style?


I'm not seeing this on Firefox or Chromium with the latest RGH version (21.2.1
).
posted by cheap-glitch about 4 years ago
It works in every browser for me. I've only seen that happen when you disable the extension in Firefox after it runs since it removes the stylesheet (while the new dom elements remain)
posted by fregante about 4 years ago
I remember when I check the style I got a code, ... {font-size: 12px}
, and it's from github server, I should wrote down that css file url, I'll check again if problem still exists tomorrow(on phone right now).
posted by fisker about 4 years ago
I can still see it

The style sheet url display a scss file

And my browser is ms edge 90.0.793.0.
posted by fisker about 4 years ago
The ridiculous part here is that our selector is already more specific than theirs, so Iām not sure of how it could happen in the first place.
posted by fregante about 4 years ago
I tried to find where it come from, not very sure but most possible is from github self, I think they updated it, but still testing.
Do you think it's safe to add font-size: inherit
?
posted by fisker about 4 years ago
Do you think it's safe to add font-size: inherit
?
That means 1em
(or whatever the title has), which would be too big, and wouldn't solve the issue because it'd still be overridden.
possible is from github self
The source points to it, so yeah. It might just be an Edge issue š¤
posted by fregante about 4 years ago
because it'd still be overridden
Sorry, I didn't notice .rgh-
class already set font-size.
posted by fisker about 4 years ago
It might just be an Edge issue š¤
All signs point to it. It works well in every browser and the selector should definitely override it.
As a quick fix you could apply some custom CSS to fix it locally and/or you could report it to Microsoft.
Closing because Edge isn't directly supported (none of us use it) and because this is a browser bug.
posted by fregante about 4 years ago