I'm using a pictograph web font called Entypo made by Daniel Bruce for a project, which does not work properly in Safari 5 for Windows. Yet the font works fine for Chrome, Firefox, Internet Explorer, and Opera.
Here's the character map. Open the link in Safari and you'll see missing pictographs. It seems like the unicode codes with 5 characters or more are throwing off Safari. Any idea why?
check this out.
http://www.open-logix.com/webtech/use-custom-webfontspictograms-in-5-steps/
I did some test with lots of browsers and even the different types of elements. Try testing it with span,div, and many other ones to see if there is a most compatible element tag.
There are issues on different browsers outside of safari as well, so don't be discouraged.
Take a look here: https://github.com/danielbruce/entypo/issues/14#issuecomment-19171286
I think this should "solve" your problem.
Related
I am building a website for a friend and it's just about done, apart from a bit more content, but now he tells me that it doesn't look right on his iphone. I have checked it on Safari, Opera, IE, Chrome and Firefox on laptop, and on my Android phone and on web-based iphone emulators and everything looks fine. I had him check on someone else's iphone and 1 of the problems goes but the other remains. My site is pretty basic, html and css only, but I am the first to admit that as I am new to this my code could probably be better.
The first issue is that above the header his iphone shows there are what's best described as 5 red bricks evenly spaced along the top. This doesn't show on his mates iphone.
The second issue is that on the "products" page, the right column text under the pictures isn't lined up properly, which is the case on his mates iphone. I don't know what to do here because if I alter the padding I used to line things up, it won't be right on every other browser/device.
I'm not sure what I'm best posting on here, the whole code for the site seems too much, but whatever needed to help answer just let me know. The site address for the products page is http://www.doortodoordrinksyork.com/products.html
Like I say I'm new to this so please keep answers simple.
Thanks in advance.
David.
PS Would appreciate anyone with an iphone telling me how the site displays on it.
If you use a Mac, you can use the iOS Simulator tool that comes with XCode to test out your site in a virtual iPhone/iPod. You can even compare different versions of the built-in browser, which I think is what's causing the difference between your mate's devices.
In general, well-built sites will 'work' without modification on mobile devices, but you may want to look into media queries, a CSS feature that lets you target specific screen sizes with different rules.
I am creating an PhoneGap application for iPhone.
When I am designing and testing HTML file in PC-Browser it looks different.
And In Phone gap it looks different.
Actually CSS not functioning as accepted. Is this known issue? OR Am I missing something?
I can provide code snippet or screen-shots if needed. Please help
Without seeing code this is almost impossible to actually answer. BUT I will say this - with mobile you are using Webkit, meaning that anything in your CSS that referes to -moz- will not work. Also, you're dealing with a version of webkit, not the newest, and not the oldest - well that is unless your on android 2.2.2
You should be safe to use any -webkit- syntax in your CSS, but just know that certain properties may not be supported in android as they have fragmented their phones quite and bit and have shipped a somewhat old version of webkit with specific OS's.
iPhone you should be all good to go, now if you continue to have issues that are more specific I would recommend you post your code so we can see what is going on - you could just have some weird markup somewhere.
document.documentElement is a DOM1 property and so was specified more than 13 years ago. In my experiments, it's reliable in IE6 onward and in vaguely recent versions (I haven't gone back far) of Firefox, Chrome, Safari, Mobile Safari, Opera, and Konqueror when I use the HTML5 doctype. So that covers a fair range of layout engines: Trident, Gecko, WebKit, Presto, and KHTML.
(It even works if I omit the actual html tag in my markup [which I'm allowed to do in HTML5 — and apparently even IE6 adds it in for me despite it never having heard of HTML5 — but almost certainly never will in practice].)
Is there any significant browser — Blackberry? Android? — in which I cannot assume document.documentElement will be present and will refer to the root html element in an HTML document?
Depends on your requirements. Older versions of Blackberry's Browser, before version 6 of the OS, may not have had support for it. But the browser was so bad that any JavaScript enabled site hardly worked anyway.
According to Wikipedia, all major rending engines support it. It seems like that table is using the IE version rather than the actual version of Trident. Trident (IE), Gecko (Firefox), Webkit (Safari, Chrome), and Presto (Opera) all support it. The Tasman rendering engine is largely obsolete and unused. I wouldn't worry about it.
In my personal experience, I've had no problems from myself or customers using that property on a reasonably modern browser.
All mobile browsers, Safari/iOS, Android, even Internet Explorer on Windows Phone 7 support it. Recent BlackBerries do as well.
So, I use the same fb-like plugin (fbml based one) code on 5 different pages on the website. The only difference is the different data in meta description and type of content. All pages were checked through the fb linter and it says everything is okay. All the buttons work alright in Chrome under Mac OS, but in Firefox, Opera (Mac & PC) and Chrome on PC (Windows) 3 of these buttons do not appear and none of them work in Safari on Mac. I can see that fb scripts are working some way, you can see the code with built-in developer tools in Opera or Chrome, and the element does occupy the space, but the button is not shown...
I've tested all the code in the pages including html, js and css line by line and it looks like it doesn't affect the fb-likes. I've also take the code from the page with the problem fb-like and make the new page with the only difference in fb-like href property - and it works. But when I change the href to the address of the page where like button didn't work - it stops working. So as I understand the problem is not on the website side, but since the fb-linter doesn't show any errors the problem is not on fb side either. But where is it then?
I've contacted the fb developers team, but I guess it may take them extremely long to answer , so I'd like to know if sombody had such a problem before. Any opinions or thoughts are appreciated!
Here's the website.
Thanks in advance everybody(:
~
I have been having some general problems with TinyMCE inside Opera. Some of these include:
the save button produces an error
when submitting to a popup with an entire form, including TinyMCE, nothing gets posted to the popup (when TinyMCE is removed it works fine)
Has anyone else experienced these errors and/or does anyone have a solution to make TinyMCE more compatible with Opera?
TinyMCE is not the only rich text editor for web. You could even try a what you mean editor or some Flash based solution.
I recommend CKEditor, it works like a charm on Opera and is also very configurable and powerful. I also had some issues with TinyMCE using the latest Opera to date (v12.15).
It depends on the version of Opera Mini you are using. The supported version is v.50 and above. The Opera Mini version 52.3.21517 and above are the supported version for TinyMCE. You can get the version 50 of opera mini mobile browser here https://press.opera.com/2019/02/19/opera-for-android-hits-version-50/