-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
Mention tips on GitHub doesn't work #1108
Comments
Does it help to use a Firefox 60 user-agent for Github? - |
@laniakea64 No. |
Did this only recently stop working with Waterfox Classic? |
@grahamperrin No, as I remember this worked sometime ago on Waterfox, but I don't remember when it was. |
I would like to confirm what @hawkeye116477 had reported regarding Waterfox Beta v56.1.0 (ARM). I actually don't recall this ever working. My own workaround was to use the "Request Desktop Site" setting. I just toggled the TBH... I just noticed this reported issue and was happy to get it working again using that suggestion... LOL! :-) EDIT: I've been using the ~Ibuprophen |
I should probably tell if it's on PC or smartphone, but that 56 version for Android isn't even on Google Play now, so I didn't take it into consideration. Anyway I talked about stable version for PC. |
Yes, the Beta version is still available. I can see it in the Play Store as seen by the attached screenshot I had just made. ~Ibuprophen |
I, too, saw an installed version. On my Android I had (2018-08-18) beta version 60.1.0 but as expected – #1085 – this morning after I uninstalled, I could not find any version to reinstall.
Maybe more than that, at least for users of Refined GitHub 19.1.31.1822. I have lost the ability to automatically preview the title of an issue (a tip) whilst writing. This feels like a very recent loss – like, within the past few days – so re: https://redd.it/ctttof I guess that it coincided with the reported end of support for legacy markup. |
With Waterfox Classic 56.2.13 (20190822231313) on FreeBSD-CURRENT. |
|
Possibly related => https://bugzilla.mozilla.org/show_bug.cgi?id=1443722. |
Just curious... If changing the Does changing the Thanks a Bunch! :-) ~Ibuprophen |
@Ibuprophen Yes, same negative effect. |
I understand now... Thanks for the clarification! :-) ~Ibuprophen |
Just to mention: this did work for me until about 2 weeks ago. Stopped working around the time I updated to 56.2.13 – both on Linux and Windows (and stays broken with 56.2.14). Playing with the UA didn't fix it here either. Another strange thing starting at the same time, but only on Linux: in the navigation bar on top, the "More" menu stayed open right from the time of loading the page. Fixing that one was rather easy via a userstyle. In case somebody else is affected: @namespace url(http://www.w3.org/1999/xhtml);
@-moz-document domain("github.com") {
.btn-link.reponav-item:hover + .dropdown-menu-content.js-menu-content, .dropdown-menu-content.js-menu-content:hover { display:block !important }
.dropdown-menu-content.js-menu-content { display:none; }
} |
Thanks,
Cross reference: |
Uh, yes, that – and thanks for spreading the word 😄 Now we just need someone to come up with a userscript. Though I'm afraid that is not that easy. OTOH I wouldn't wonder if that could be done by comparing page source in WF with the same from a browser where it works. Wouldn't be the first time Github omits script entries based on browser, so maybe we'd just need to insert that back. Anyone tried with a Chrome-based UA string, for example? Though I'm not sure what that might break then… |
For @… completion, yes? @github | cc @ACyphus re: #784 (comment) in November 2018, GitHub granted a UA-oriented whitelisting, for Waterfox to continue working normally. Thanks again for that. Now – for this recent mentions issue – is another whitelisting possible/appropriate? TIA for any advice |
Yes. That stopped working for me at about the time I updated to 56.2.13. Which includes the "tips". And aren't those @… thingies called "mentions"? I thought we're talking about the very same thing: You start typing the "@", then usually a "tip" opens listing participants in the thread (plus the owner of the repo, if I got that correctly). Thanks for the link – it seems that yes, another white-listing might be required (Github staff should be able to tell). |
I do think so. (I threw the phrase @… completion into the mix partly for search engine purposes, because other people might use words such as complete or autocomplete or auto-completion.) |
@hawkeye116477 re: your other comment yeah, I, too, have doubts. (Re: polyfills, I saw your recent |
Seems that GitHub/Microsoft fixed this. |
Confirmed: It magically started working again yesterday. As for the "More" button, that was only half fixed: the drop-down now is completely hidden and doesn't open even on click. My UserStyle still fixes that. |
This, too, appears to be fixed: Thanks @github
(Not a feature of GitHub.) |
|
Oh. Good guess I guess, I'm using that… Thanks! And uh, you've linked me that before and I didn't get that part, shame on me… |
NP :) |
When I want someone mention, then usually tips should be shown about who I want to mention. This works on Vivaldi and Firefox, but not on Waterfox 56. Can this be somehow fixed/implemented on Waterfox's side?
On console I have error
TypeError: customElements.upgrade is not a function
, it seems that disappears when I setdom.webcomponents.customelements.enabled
totrue
, but mention tips still doesn't work.The text was updated successfully, but these errors were encountered: