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

Pull Quotes Display Enhancement #91

Open
grayghostvisuals opened this issue Mar 20, 2013 · 10 comments
Open

Pull Quotes Display Enhancement #91

grayghostvisuals opened this issue Mar 20, 2013 · 10 comments

Comments

@grayghostvisuals
Copy link
Contributor

Here's the idea to give more variety with pull quotes in terms of quote placement. This would be done by passing a string of the authors choosing which depicts the location of the quotes.

@include pull-quotes($font-size, $opacity, 'quotes-left');

'quotes-left'
'quotes-right'
'quotes-both' 
'quotes-none'
@KittyGiraudel
Copy link

Regarding pull quotes, you definitely should encode and in the stylesheet.

Safari 6 doesn't like non-encoded symbols in CSS. I had the problem on my own site and on browserhacks.com.

@grayghostvisuals
Copy link
Contributor Author

@hugogiraudel So it doesn't matter for Safari 6 even if UTF-8 is supported?

@KittyGiraudel
Copy link

@grayghostvisuals
Copy link
Contributor Author

@hugogiraudel So I went back to Snow Leopard w/Safari 4.0 and it actually does support non-encoded, recognized UTF-8 characters like quotes. This means you don't need \201C as you've been using. You can even go back to the iPhone 3GS and see that it does in fact have support as well.

@KittyGiraudel
Copy link

Issue on browserhacks.com: 4ae9b8/browserhacks#53
Issue on hugogiraudel.com: https://twitter.com/Macxim/status/311052134051373056

@grayghostvisuals
Copy link
Contributor Author

Here's an example using Typeplate pull quotes and non-encoded characters in the content: "" property. This was also used for my testing that I noted above.
http://cdpn.io/cvqmk

Windows 7 on IE8 still seems to be a bugger.

@caycefischer
Copy link
Member

Wow, that's a real shocker to me. I had no idea, I've been using unicode in CSS for ages.

Argh.

Well, how comfortable are we phasing out IE8 support? Personally, I don't mind :P

@KittyGiraudel
Copy link

@caycefischer
Copy link
Member

That's interesting, very neat. But the premis is flawed—the content value
doesn't have to be an escaped value.

– Zachary Kain

Designer, Developer
Writer, Educator
416-712-8895
[email protected]
http://draftingcode.com

@grayghostvisuals
Copy link
Contributor Author

Besides all this hullahbahloo I think the :lang pseudo class selector would be cool to use in order to throw the @mixin an argument for languages that have quotes which differ from the standard and depressing english language.

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

3 participants