BlueOwlCreative » Topic: Logo Looks Odd https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/feed/ Thu, 27 Aug 2026 13:22:52 +0000 http://bbpress.org/?v=2.5.3-5249 en-US https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29404 <![CDATA[Logo Looks Odd]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29404 Fri, 08 Jul 2016 11:57:46 +0000 esgoddard Hi, my logo displays strangely when I view the website on a Windows phone (please see screenshot). This has happened before for me with Fortuna. How can I fix this? Many thanks

https://1drv.ms/i/s!Amda9qLt1GBQgjjVOCUj6s7fSRbd

]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29406 <![CDATA[Reply To: Logo Looks Odd]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29406 Fri, 08 Jul 2016 11:58:03 +0000 esgoddard https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29412 <![CDATA[Reply To: Logo Looks Odd]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29412 Fri, 08 Jul 2016 12:13:17 +0000 BlueOwl Can you try uploading a smaller logo (win browsers/os have a hardtime resizing images at times + you don’t need a logo 600px wide! Try uploading a 150px wide version!

]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29429 <![CDATA[Reply To: Logo Looks Odd]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29429 Sat, 09 Jul 2016 09:58:54 +0000 esgoddard Thanks, 150px makes it too small so I’ve put it in at 300px. This is how it looks good on desktop. Unfortunately it still gets cut short on those mobiles but I’m guessing there is no way round this other than shrinking my logo…

]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29435 <![CDATA[Reply To: Logo Looks Odd]]> https://blueowlcreative.com/support_wp/forums/topic/logo-looks-odd/#post-29435 Mon, 11 Jul 2016 09:14:29 +0000 BlueOwl Hi,

Just got my hands on a Win phone (those are rare to find!) and reinspected this.
Indeed, looks like some real browser specific bug… As the problem can’t be reproduced in Chrome devtools (Lumia device mode) it’s hard to find out what’s going on there.

]]>