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

li3.me website has lost indentation on code examples #78

Closed
kevin-jones opened this issue Jan 29, 2015 · 8 comments
Closed

li3.me website has lost indentation on code examples #78

kevin-jones opened this issue Jan 29, 2015 · 8 comments

Comments

@kevin-jones
Copy link

Looking at code examples on pages such as http://li3.me/docs/manual/model, the indentations have disappeared!

@nateabele
Copy link
Member

Hmm. We recently changed Markdown libraries, so it could have something to do with that. I'll look into it next week. Thanks.

@mariuswilms
Copy link
Member

@kevin-jones Can you point me to the pages where you see the indentation ist lost? To me this looks all correct: http://li3.me/docs/lithium/data/Model::find() http://li3.me/docs/manual/models

@kevin-jones
Copy link
Author

For example: http://li3.me/docs/manual/models

It does look correct for me on http://li3.me/docs/lithium/data/Model::find() however

@kevin-jones
Copy link
Author

Could be a browser compatibility issue - it does work for me in Firefox, but not Google Chrome

@mariuswilms
Copy link
Member

I'm using Chrome, too. I've attached a screenshot.

bildschirmfoto 2015-01-30 um 13 38 42

@kevin-jones
Copy link
Author

Strange... perhaps local to me then, I'll investigate.


This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com


@kevin-jones
Copy link
Author

Checked with several others in the office here - they see the same as me (broken in Google Chrome version 40) but fine in other browsers.

Also as mentioned above the indentation in the API docs is fine, it's just the manual that is affected.

@mariuswilms
Copy link
Member

@kevin-jones I can now confirm the behavior (I was still on Chrome 39). This seems to be a known issue and a regression in Chromium 40: https://code.google.com/p/chromium/issues/detail?id=446434

I'll be switching optimizeLegibility off for the time being. The changes should come in effect with the next deployment of the site. Thanks for reporting the bug.

UnionOfRAD/site@1373eb5

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

No branches or pull requests

3 participants