They look a little odd to me, the pause is spaced much further away from the text than the play, was that the intention?
Nothing should have changed layout-wise on the v1 skins since last update. Has anything else updated on the site?
fyi the v1 skins don’t support so well the new sizing options, they’re offered largely for continuity support when coming from v1.x of the plugin. The buttons won’t scale which makes the vertical alignment look odd.
hi simon,
here’s the same link with the css fix taken out:
http://carinemontbertrand.com/audiobooks/
click play and you’ll see what I needed to fix.
Also note the difference between the position of the pause button for the V/O Reel player vs. the other samples.
This happened with all players across many sites.
Let me know if you have another suggestion.
thanks,
jp
I just switched to Light (not the legacy support version), and the pause button also has a position issue.
See this url: http://501.407.myftpupload.com/audio/
With this version of the player, this css put the pause button to the center of the button’s outlined container:
span.gfxbutton_mp3j.pause-mjp {
background-position: 5px -3px!important;
}
Hi James, that’s odd, could you try without the fix in a default theme?
The images on those are positioned to centre both horz and vert. I suspect it’s something in the theme css that is over-ruling.
The problem with a fix like that is it only works for one size of player that you’re fixing it for.
Yes, it works just fine in a default theme, although there is still a little sliver peeping in from the right of the next sprite image:
http://jameseverlydesigns.jimpoulos.com/hello-world/
Yeah, it’s strange. It was something to do with the span for the play pause. The themes I’m using are from Elegant Themes, and I can’t pinpoint where to find the conflict. They are a pretty common Theme company. Any ideas are welcome. Aside from standard browser resets and some font-sling, the only css on the player that I can see using a Web Inspector are coming from the plugin’s css, not the theme.
I marked this resolved as a theme conflict.
