You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing a PR as well as browsing to the code directly, I'm seeing URLs in the code being replaced by Refined Github.
When I do a search for the content that is different, I can see in the search result preview the real content. When I then click on the search result to open the exact file, it shows me the wrong content.
I have verified this is caused by Refined Github as enabling/disabling it makes it work/break.
When refreshing the page I can see for a fraction of a second that the first load contained a different diff than what I end up with so I'm certain something is replacing it.
Through trial-and-error I have found that the offending feature is linkify-code. This seems relevant because the code that I am looking at is a dictionary where the keys are URLs:
When viewing a PR as well as browsing to the code directly, I'm seeing URLs in the code being replaced by Refined Github.
When I do a search for the content that is different, I can see in the search result preview the real content. When I then click on the search result to open the exact file, it shows me the wrong content.
I have verified this is caused by Refined Github as enabling/disabling it makes it work/break.
When refreshing the page I can see for a fraction of a second that the first load contained a different diff than what I end up with so I'm certain something is replacing it.
Through trial-and-error I have found that the offending feature is
linkify-code
. This seems relevant because the code that I am looking at is a dictionary where the keys are URLs:With the feature enabled, this becomes
Notice how the url ends with
&url=[referrer_url]&correlator=[timestamp]
-- it feels as if the parsing is going wrong somewhere.I've disabled the feature for the time being so I'm unblocked on this.
The text was updated successfully, but these errors were encountered: