Skip to content
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

Tacit logo missing for Android 2.3.3 default browser #147

Closed
filfreire opened this issue Mar 18, 2018 · 15 comments
Closed

Tacit logo missing for Android 2.3.3 default browser #147

filfreire opened this issue Mar 18, 2018 · 15 comments
Labels

Comments

@filfreire
Copy link
Collaborator

filfreire commented Mar 18, 2018

How to reproduce:
On Android 2.3.3 default browser, visit yegor256.github.io/tacit/

Screenshot:
android_233_480_800_002

EDIT: This could be a simple fix. Currently, the image being loaded is an SVG, and that browser version in particular could have an old version of Webkit that doesn't support SVG standards.

@filfreire
Copy link
Collaborator Author

@yegor256 please label this issue as bug.

@filfreire filfreire added the bug label Mar 20, 2018
@0crat
Copy link
Collaborator

0crat commented Mar 20, 2018

Job #147 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Mar 20, 2018

Bug was reported, see §29: +15 points just awarded to @filfreire/z

@0crat
Copy link
Collaborator

0crat commented Apr 12, 2018

@filfreire/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link
Collaborator

0crat commented Apr 17, 2018

@filfreire/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link
Collaborator

0crat commented Apr 22, 2018

@filfreire/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link
Collaborator

0crat commented Apr 27, 2018

@filfreire/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented May 2, 2018

@filfreire/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented May 7, 2018

@filfreire/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented May 12, 2018

@filfreire/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented May 18, 2018

@filfreire/z everybody who has role DEV are banned at #147; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented May 23, 2018

@filfreire/z everybody who has role DEV is banned at #147; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

filfreire added a commit to filfreire/tacit that referenced this issue Nov 23, 2018
@filfreire
Copy link
Collaborator Author

Closing this issue, should be fixed after release of tacit 1.3.5. Currently having trouble re-testing to see if the fix worked.

@0crat
Copy link
Collaborator

0crat commented Dec 1, 2018

Job gh:yegor256/tacit#147 is not assigned, can't get performer

@0crat
Copy link
Collaborator

0crat commented Dec 1, 2018

The job #147 is now out of scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants