-
Notifications
You must be signed in to change notification settings - Fork 192
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
"G takes you to github..." on mobile #572
Comments
Agree re. the link. And I notice now we don't have a similar message on individual issue pages but I think we should. |
Yes, second that. Thanks @tagawa |
Ah, forgot about this issue: #449 (comment) Looks a little goofy. Should we just left align it and call it a day? |
I'll defer to @calexity's design sense. |
I thought I responded to this, and it looks closed, but I think left-align or center-align should be fine, if it's still an open question. |
You have have @calexity -- sorry if I missed that. I'll pick left or center and we can deploy the fix today. |
* master: (46 commits) Fixes #509 - mention [ci skip] in docs. v1.6.2 changelog Issues #588 - list style Fix #583 Using the function for checking dependencies Checking dependencies Modules needed for checking dependencies Two cases to handle Adding message Issue #368 - Remove (now) unused STARTUP variable Issue #368 - Compute cache busting param based on md5 hash of file Issue #368 - Move bust_cache function into a Jinja template helper Issue #368: Part 1, add bust_cache param to minified production JS Issue #587 - Add a task to check npm dependencies and run by default v1.6.1 Fixes #591 - Typo in form field. >_< Tag v1.6.0 Issue #572 - Remove right float for GitHub issue warp hint Issue #432 - Add js-form-error and js-no-error classes and update tests. Issue #432 - Add wc-Form-required class to problem label Added wc-Form, wc-ReportForm ...
On the All Issues page -
I think we should link this message to Github rather than confusing people.
Possibly should do the same on Desktop. Either type g or just click the link.
Thoughts @karlcow @miketaylr @magsout
The text was updated successfully, but these errors were encountered: