This image above was taken by my trusty Olympus PEN (E-PM1). An older (2011) and lowest end of that line of cameras. But evidently still better than phones… See the rest of the post →
Dear #content and #contenttext of my site,
I’m not quite sure why you’re defiant, but I would really appreciate it if you would respond to my @media queries. You’re good on the desktop, you have moved to the appropriate place and did everything appropriately and for the most part, behaved well for regular use. But that is less so it seems when it comes to the @media queries. Maybe I’ll saying everything wrong, I don’t know.
#contenttext, you are pretty well behaved except when it come to scaling text on mobile devices. Why are you so small in Dolphin See the rest of the post →
Well, there we have it. Nearly a week into Pacific Stupid Time. Also known as UTC -8:00 or GMT -8.
Now it might be okay if Pacific Standard Time was standard. Except it’s not. After the daylight saving time change was changed a few years ago, eight months out of the twelve months we are now on daylight saving time. So what’s the point of standard time when it isn’t even standard time? There isn’t any. It’s just Pacific Stupid Time. Yeah, so you get to sleep in a hour…big whoop when you lose that hour just a few months See the rest of the post →
It does out the mosaic photo layout doesn’t display properly in all computers. Arghh! The tiled one looks relatively ok though.
Not as maddening as my blog not loading in Chrome on WinXP or at least’ my sister’s computer… See the rest of the post →
I don’t get it. The blog won’t show up on Chrome (yes, the latest version) on Windows XP. The backend, however still works (accessible only through the url and I can write drafts etc) but it will not load the blog itself for more than a few seconds before going “aw snap”. It’s not my server as my hand coded site works. I tried disabling plugins and that didn’t change anything.
It is possible it’s just that computer as it’s the only Windows XP computer at this time. But I tried playing with the firewall and still no go. The See the rest of the post →
You’ll think that Google web fonts will work well in Google Chrome. Well, no. And it was WORSE before too!
In <h1> titles, at least with my font (amaranth) – an ellipses (…) can make it revert to the fallback font. If you have a comma, then the text on the other side of the comma that is not with the ellipses will display the webfont. Weird eh?
Firstly I don’t understand what’s with the “read more” link and why it seems to be doing its own font thing even though I’ve told it not to. (I’ll let it go See the rest of the post →
Welcome to my blog on a new theme!
I am using a custom child theme of the default Twenty Twelve theme. It features a modified featured image, custom width sizing depending on the size of monitor (it’s also slightly wider on most larger monitors than the original), footer widgets and a generally different style.
My fonts are Zeyada (title), Amaranth (headings) and Lora (body). (Although I still might change it). All fonts are from Google webfonts for now.
This blog is best viewed on a higher resolution monitor (such as 1500px+) with a newer browser. It does work on See the rest of the post →