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

Social buttons need tweaks #2628

Closed
corysimmons opened this issue Mar 18, 2016 · 14 comments
Closed

Social buttons need tweaks #2628

corysimmons opened this issue Mar 18, 2016 · 14 comments
Assignees

Comments

@corysimmons
Copy link

https://amp-partners.appspot.com/social demo looks good but the Twitter logo isn't retina friendly (it isn't svg whereas the others are), and it doesn't look like Facebook is displaying properly at all.

image

Also is there a reason these have border-radius? It's not built in is it? Perhaps we shouldn't encourage additional styles (to disable pre-existing styles) where possible?

@jaygray0919
Copy link

The demo displays in Chrome and Safari as shown be @corysimmons. In Firefox, however, only the two Twitter images display. The four images to the right of "Moo!" are color boxes. Anyone else see this condition? Is there a Firefox setting that, if turned off, would show only the color box and not the icons?

@dvoytenko
Copy link
Contributor

/cc @paul-matthews could you please take a look?

@rudygalfi
Copy link
Contributor

I believe @paul-matthews will be unavailable for a couple weeks.

@rudygalfi rudygalfi added this to the Sprint 2016-03-31 [current] milestone Mar 24, 2016
jsit added a commit to jsit/amphtml that referenced this issue Mar 25, 2016
… in amp-social-share elements of any width/height (other than 60x44) (Issue ampproject#2628)
dvoytenko added a commit that referenced this issue Mar 25, 2016
Add Twitter background SVG to amp-social-share CSS (Issue #2628)
@ericlindley-g
Copy link
Contributor

@dvoytenko , who's a good person to take a look at this while Paul is unavailable?

@dvoytenko
Copy link
Contributor

@ericlindley-g I think these are all done. Can we confirm this?

@rudygalfi
Copy link
Contributor

Rolling this into next milestone.

@ericlindley-g
Copy link
Contributor

@mkhatib , could you check locally to make sure the issues on this page are fixed? (Twitter icons should be SVG; Facebook icons should show up, rather than displaying "Moo!")

@mkhatib
Copy link
Contributor

mkhatib commented Apr 5, 2016

@ericlindley-g I confirmed that twitter icons are SVG. For FB this is actually working how it was designed to work. When the user provides their own anchor element it's assumed that they want to style it themselves hence our styles are not applied.

This is somewhat confusing and I am working on a way to make this less confusing. But in the example provided if you remove the custom DOM elements the FB icon and styling would show because our defaults kicks in.

I am working on a way to streamline this somehow.

@ericlindley-g
Copy link
Contributor

Thanks for checking—I looked at the example more closely after your response, and I see that it's working as intended.

on Firefox, though, I'm seeing the issue that @jaygray0919 reported (only colored squares, without logo content, after the "moo!"s). Would that be something you could take a look at, too? Happy to open another issue to track, if that helps.

@mkhatib
Copy link
Contributor

mkhatib commented Apr 5, 2016

Ah sorry missed that part. You're correct this does seem to happen on firefox. From MDN:

Note: as of Firefox 6, fragments (anchors) are processed consistent with other URI schemes, thus a bare "#" in the content needs to be escaped as '%23'.

I confirmed that replacing all # in the fill= attribute with the escaped %23 seems to fix the problem.

No action is required though, it seems this has been fixed in #2665. The example link given uses its own build of AMP and not our production or canary one hence you won't be able to see latest changes to that example page. I created this JSBIN where you can preview the latest changes - you still need to toggle the experiment by running AMP.toggleExperiment('amp-social-share') in the console in that page.

@ericlindley-g
Copy link
Contributor

Looks good! @mkhatib, you mentioned above that you're working on making the behavior a little less confusing, but it seems like the issues here are largely fixed or working as intended. Would you like to leave the issue open for any additional work you're doing, or can we close it?

@mkhatib
Copy link
Contributor

mkhatib commented Apr 6, 2016

I'd keep this as the general tracking bug for the changes - but I am ok with closing it as well.

@ericlindley-g
Copy link
Contributor

Rolling into the next milestone

@mkhatib
Copy link
Contributor

mkhatib commented Apr 29, 2016

Closing this, please open separate issues if anything is still not addressed by the last PR.

@mkhatib mkhatib closed this as completed Apr 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants