Chrome or FF as IE-component replacement? - google-chrome

I'm currently launching IE w/o toolbars/url from NAV to get a more clean experience.
IE has rendering problems, (related to opacity etc) so:
Can I start FF or chrome w/o toolbars and set width/height. I'm browsing through the command switches, cannot find a way to turn off tabs etc though.
Thankful for any advices. IE, as always, drives me nuts.

all projects on FF seems dead currently,
Chrome has the feature natively,
http://support.google.com/chrome/bin/answer.py?hl=en&answer=95710
Over and out.

Related

Text flow out of divs in chrome, but not on all chrome users?

I got a really strange problem, and after so much tries and research I can't get out of it.
I have a website, but SOME (just 5% of visitors) people with the SAME version of chrome, see the text flowing out of divs and text overlapping. It's very strange because I tested the website on all chrome browsers using browser testers, without any problem. And in internet explorer or firefox this problem never happens...
A page is located here
And here are some screenshots of what SOME people see (maybe you won't see this in chrome)
click here
Maybe it is because of the font face I am using? Or maybe some bad coded CSS?
Please help me out of this!
Thanks a lot!
I see you use .svg font. Recently I was hunting some Chrome font rendering bugs and saw this:
http://code.google.com/p/chromium/issues/detail?id=95102
This seem very similar to issues you are having. You could try to serve some other font type to Chrome and if this would fix that.
If you don't want or can't serve some other font type to Chrome, the only thing you can do is wait until Chrome version 24 is out to all users which should be soon (I can't find any announcement)
I tested it in
Chrome 23.0.1271.97 m
Chrome 26.0.1371.0 canary
Chromium 25.0.1334.0 (169326)
# Windows 7 x64 and your page seems fine for me.

CSS3 Transitions Not Working On Specific HREF

For some reason, on this page, in Chrome 17, CSS3 transitions aren't working the first 3 links in the footer/nav: http://jacob.bearce.me/index2.htm. The links are exactly the same, no added classes, and I went through step by step to figure out what it was, it's changing the HREF property that breaks them. For some strange reason, services.htm works, but projects.htm does not. I have absolutely no idea why.
UPDATE: Tested in Firefox, Opera and Safari it seems to be only a Chrome issue. It makes no sense. It's not even a webkit issue (unless Chrome's got a newer version than Safari).
Sorry if this response is slightly late, however, I'm currently on Google Chrome 16.0.912.63 beta-m and I have the exact same problem as you do. In fact, on your website, out of the 4 links below, it is only the home link that doesn't seem to be working too well with CSS3 transitions (on my side).
On a website I'm currently working on, the transitions seems to only work on some links and not others. I can't really see any trend to understand what causes it. Strangely though, when I visit your website or mine through Incognito, everything works well. It doesn't work even with my extensions disabled.
It looks to be bug with Chrome. I've figured out that it's definitely an issue with :visited links, but can't fix it no matter what. In incognito mode you don't see the issue because Chrome isn't logging what links you've visited. From what I've seen, it looks like it's an issue in Chrome 16 or higher. Hopefully they'll fix this in the next release, but for now, we'll just have to ignore it.

Making chrome/FF render text as nicely as IE

I'm working on a site for a client and they've asked for a fix for the font rendering in FF and Chrome not looking as good as it does in IE. Here's a screenshot:
Does the IE text on the left look nicer because it hooks into Windows Cleartype, and FF doesn't? I think there is nothing i can do about this, am I right?
I don't think there is anything to be done about this. While IE does use ClearType fonts by default (this can be turned off in Tools > Internet Options > Advanced (tab) > Multimedia (settings option) > "Always use ClearType for HTML" (checkbox) ), turning it off doesn't seem to change the fact that IE will render text slightly differently than FF, Chrome, Opera etc. Even if it did fix it, it's a client-side option so you'd still be out of luck.
So, yeah you're stuck with some difference in text rendering based on the browser.
HOWEVER, you can try google's web fonts:
http://www.google.com/webfonts#ChoosePlace:select
They seem to look very similar cross-browser, though I see a slight difference between IE8 and FF5.
Plus, they look pretty cool and you don't need to install them on your system to use them.
There is no way to activate this from your website. Window's ClearType can only be activated in other programs via Windows' settings. It's not a browser feature, it's an OS feature.

My HTML5 webpage is not being read correctly in IE 9

Hello my website http://www.paruhdice.com/index2.html is not acting as it should be. It worked some what fine in IE 8. And works perfectly in the latest CHROME and Firefox... but my sliding navigation is not even responding. What should I do? Prompt users to use CHROME or FIREFOX... or is there a fix to this? Thanks ahead of time
It seems to be working for me in IE 9.0.8112.16421 as well as the latest Firefox release. The left-hand navigation bar moves smoothly with the window as I re-size.
Unfortunately, HTML5 is not a fully implemented standard, so you won't get full support in any browser. IE9 was also released back in march and both Chrome and Firefox have made great strides since then to add more support for HTML5. Doing a quick web search I came up with the site, http://html5test.com/results.html. It certainly gives an interesting overview of your current browsers support for html5 as well as the ranking of other browsers by comparison.
Since it all ready sounds like you are telling all of the old IE, Safari, Firefox users to update to view your site, I see no reason to tell them some features don't work and you recommend they upgrade.

How to solve the problems that html page works well in firefox and chrome, but wrong with IE?

I meet a problem that my page works well in firefox and chrome(almost the same look and feel) but very bad in IE. It's time consuming to adjust the differences. Is there any research has been done already to tell the differenceS, or any automation tool to examine the uncompatibilities?
BTW: which tool you guys are using when debugging in IE(like firebug for IE)?
Your best starting point is to always use some kind of "reset mechanism" like Eric Meyer's CSS Reset or framework like HTML5 Boilerplate, they help in reducing differences between browsers (not all, but most of it). If this is not possible (project is already in finishing phase, etc.) you can always ask questions here, check Position Is Everything for description of bugs, Quirks Mode, SitePoint reference and various other sites (Google is your friend :)). Hope this helps.
There is "debugging" tool for IE - IE Developer Toolbar - but it's usefulness can't compare to that of Firebug, Dragonfly and such. IE8+ does have better support for debugging, though… There are some articles that suggest using Visual Studio, but I haven't tried it. Mostly it's just trial and error with IE :).
ie7-js is a JavaScript file that automatically fixes many Internet Explorer bugs for all versions. Works like magic.
For fast and better results in IE you can use CSS Hacks for adjusting the HTML elements.
For IE we have IE Developer AddOn
you can download it here : http://www.microsoft.com/downloads/en/details.aspx?FamilyID=95e06cbe-4940-4218-b75d-b8856fced535
Welcome to the tiresome world of IE.
IE8 has some version of developers tools, hit F12 on your keyboard and it will pop up. (not present in 6&7)
There are many documented bugs in IE, a simple Google Search would help you out better, but a lot cannot be accounted for until you have your site working in FF.
What most developers I know do is to make the site in FF, make small changes for Webkit browsers then go over to IE (not including 6) and debug.
In my experience there really is no way to tell what IE is going to mess up next, so you'll probably just have to deal with it as it happens.