Amir Dekel
Amir Dekel
@bbatsov true, no idea how I had missed [that one](https://github.com/justbur/emacs-which-key/issues/306), since I clearly remember testing it on vanilla Emacs and checking the issues on `which-key`'s repo... sorry! Anyway, I've made...
The recent commit adds a workaround which can be removed when the [upstream issue](https://github.com/justbur/emacs-which-key/issues/306) is resolved.
The line breaks are wrongly represented in the [response body](http://api.realworld.io/api/articles/Try-to-transmit-the-HTTP-card-maybe-it-will-override-the-multi-byte-hard-drive!-120863) as `\\n`, i.e. the `\` is escaped. However, this appears to be a problem with how the dummy articles were...
@myshevchuk Thanks, I'll see if I can work in it myself.
Yes, that's right. Clicking the definitions changes the highlighting, which then remains wrong until the browser forgets the visited target, whenever that may be. `Agda.css` doesn't contain any rules for...
I agree, my last paragraph was only for context.
I believe this is not an issue upstream in Agda after all, but rather a too low specificity of the selectors in PLFA's `agda{-dark}.scss` files. Check out [Agda's original `agda.css`](https://github.com/agda/agda/blob/185d9d4761db0c5a261fd449fbfef04bf9319377/src/data/html/Agda.css#L4),...
Apparently `transparent` [only works in Firefox](https://developer.mozilla.org/en-US/docs/Web/CSS/:visited#privacy_restrictions) (*sigh*) and it's indeed too much of a hack. But anyway the real issue is with specificity and there's no need to add an...
The latest commit addresses the issue on both Firefox and Chromium. `.Agda .{classname}` has specificity weight 0-2-0, while `a:visited` has 0-1-1. I can have a look on using an exclusion...