Tag Info

Hot answers tagged

10

Chrome uses the WebKit rendering engine. Firefox uses the Gecko engine. Both interpret and display type slightly differently, as do the DirectX and Vega graphics engines used in IE9+ and Opera. You can't force browsers to render text identically, but you can do a couple of things to ensure that your navigation takes up the same width across browsers: Use ...


8

Do the latest version, and a quick check with the previous if you really want. There's a post someone did a few months back with graphs showing what happens to various browsers' versions once a new one comes out. It was primarily about Chrome, because of its automatic updating, but he also saw that since 4 Firefox has been doing basically the same thing: as ...


6

It's wise to use autofocus with a JavaScript fallback for browsers that don't support it. From Mark Pilgrim's Dive into HTML5 Forms: What’s that? You say you want your autofocus fields to work in all browsers, not just these fancy-pants HTML5 browsers? You can keep your current autofocus script. Just make two small changes: Add the ...


5

Actually, Spidermonkey (FF) and V8 (Chrome) are very similar in the core javascript engine API in that both try to be standards compliant. The main difference is that Spidermonkey tends to add some nice extras to their API if they feel it is needed. All of this is found at the Mozilla Development Center (MDC) for JavaScript and well documented if it is not ...


4

Are you definitely testing the same URLs? If you are inputting your domain into one testing tool, then that checks if the home page on your site (ie the HTML) is sent gzipped. But if you open the page in Firefox and run Yslow it will check all linked files as well. Your HTML pages may be gzipped (probably as a result of a CMS) but CSS and JavaScript may not ...


4

I tried it and it works perfectly for me. Note that the color and font-size properties won't have any effect in Chrome, since no text gets displayed. (Firefox displays the alt text if the image cannot be found.) Using the width property, for example, shows that it works fine. I'll post my code below for you to see. However, to your original question, ...


4

Use autocomplete="off" to disable autocomplete and Firefox (and other browsers who support this non-standard attribute) will not save those values. <input type=text" name="dontsave" autocomplete="off"> Edit: What you're seeing may be due to the field names you are using. Auto-complete looks for common username/login field names to work and your ...


3

It all depends on what part of the world. Overall, yes Opera is the least used browser, but there are places like the Ukraine and Belarus, it's the most used browser. You can see some stats here: http://gs.statcounter.com/ Also, Opera is used a lot on mobile and console devices because of their compression services. In my opinion, I think the 2 biggest ...


3

The character is "ffi": Unicode Character 'LATIN SMALL LIGATURE FFI' (U+FB03) Why your computer is choosing a script font to handle it, I'd check your localization and internationalization settings for your computer.


3

Here's the answer from a Mozilla developer: In Firefox 11/12, SPDY support is present but disabled by default. You will have to go into about:config and set network.http.spdy.enabled to true. In Firefox 13+ SPDY is enabled by default. If you are using those and are still not seeing the SPDY icon, please try https://spdytest.com/. If that still does not show ...


3

In my opinion, Firefox, Chrome and Safari already has sophisticate development tools with default distribution. Chrome has Developer Tools and Javascript console, Safari has a Develop Menu (enable in Preference), and many more in Firefox's Web Developer. So plugin such as Web developer become a handy tool from an essential element for web development like ...


3

Your find that neither Chrome or Firefox is rendering Ambient via the @Font-Face and what is happening is that the Crusive Font is rendering slightly different in Firefox than Chrome (Very Little Difference, but its using Crusive not Ambient, Fix posted below) Chrome, and Firefox render fonts differently from one another so sometimes you notice no change, ...


2

If you write a jQuery app, you don't need to worry about anything as you are developing to a framework/library that does (today) and will continue to do (in future versions) everything under the hood. if you are writting plain javascript, then it's all a mess :) as you need not to develop your app in one browser but to test in all other browsers, and ...


2

As the attribute selector is defined in the W3C CSS spec, you should be able to use it. But browsers implementations vary, and are more or less reliable. As you can see on SitePoint Reference support for CSS attribute selector, Webkit's support is buggy. You could also see that IE's css attribute selector support varies from one version to another. Thus ...


2

When a well behaved web browser encounters cached content, it generally still requests the head portion of the cached document so that it can ensure that the content hasn't changed since it was last cached. Just as long as the last-modified or content-length changes, then you shouldn't have a problem. Issues arise when your web server has explicitly told ...


2

Just have that page send out anti-caching headers every time a user loads it. This will force the browser to get a fresh copy of the page every time. You can do this without affecting the caching of the other pages in the site. You can use meta tags: <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"> <META HTTP-EQUIV="PRAGMA" ...


2

Changing the submit button from type submit to type button will prevent the form from being submitted. http://jsfiddle.net/tfcuA/ If you click a submit button you'll need to "jam" the default submission behaviour by returning false or using jQuery's preventDefault. Otherwise have you Captcha handling code trigger from onsubmit on the form.


2

If an extension does not have official support for Firefox 4, you can choose to bypass the version checking in Firefox: In the address bar enter about:config (read & accept any warnings to proceed) Right-click and select New > Boolean from the menu Enter extensions.checkCompatibility.4 for the preference name Enter false for the preference value ...


2

I wouldn't say bad code, but bad design. Are you serious when you say that have more than 100 files to only one page? Using image sprites, only one css file, using a nice javascript library and compressing other scripts... You need to think how to deliver the minimum to client, hence each extra request takes extra time. But okay, your problem seems to be ...


2

In case anyone comes across this, for me the problem was letter-spacing. Chrome and Firefox handle the property differently. My problem was the letter-spacing was affecting the position of other elements; specifically some images in the nav menu. By removing the property my problem was instantly solved. I have also read that specifically using .point ...


2

Opera is generally less supported because it has a lower market share. It has stayed consistent around 1% for the past 5 years while other browsers have been released and "broken through". Many people don't see a reason to invest time into testing in Opera. It's also a singular entity in its own right - IE obviously has a lot of market share, and the Gecko ...


2

This is a classic error, your rule only matches paths which literally match /testword. If you want to redirect everything that begins with /testword, remove the $: RewriteRule ^testword "http\:\/\/outsidedomain\.com\/test\.mydomain\.com\/testword\/" [R=301,L] If you want to match /testword and /testword/ and nothing else, make the slash optional by adding ...


2

Is there a plugin for FireFox that will allow me to view a website as if I was looking at it in IE 6? Unfortunately not, however there are a great number of on-line services that you can use for testing, or you could also install a stand-alone version of IE6 for testing on your own PC. On-line renderers: http://netrenderer.com/ http://browsershots.org/ ...


2

It's done with JavaScript, using the window.onbeforeunload event (Mozilla, IE). Some browsers will even let you specify (part of) the text in the dialog box by returning a string from the event handler, but for security reasons, recent versions of Firefox (which you appear to be using) will ignore the string and just always present the same fixed message. ...


2

if your server is asking you to download .php files instead of displaying them, something is wrong with your PHP Handler. This should be set up already in your Apache httpd.conf file, but you can also add it in an .htaccess file like so: AddHandler application/x-httpd-php .php .html or AddHandler application/x-httpd-php5 .php .html depending on your ...


2

The fonts on various websites should offer the same experience than any other operating systems, of course they are never pixel perfect since the rendering engines vary. But with this said it shouldn't be as bad as you say it is and I imagine that something else is causing font problems on your screen, one thing it could be comes to mind and that is early ...


2

Browsers cache DNS which is separate from just clearing the cache which deletes temporary files. To delete the DNS cache in Firefox follow these easy steps: Enter about:config into the address bar If you receive an acknowledge warning click next Find a option that is labeled network.dnsCacheExpiration and set its value to 0 Restart Firefox In the event ...


1

If you inspect the request in any HTTP Debugger or HTTP Monitor (like "Net" panel in Firebug, for example, or similar tool for any other browser) you most likely will see that request to .ogg file returned 404 error despite the fact that file DOES exist. The reason is -- IIS/IIS Express and maybe the built-in development web server in Visual Studio ...


1

Try adding this line to the bottom of the user.js profile to force modal prompts: user_pref("prompts.tab_modal.enabled", true); One of the lines in user.js is likely resetting the default behaviour for Firefox 4 prompts, so adding that line at the end of user.js should override the reset and force the new prompt style.


1

You didn't mention which specific version you were working with, but there was a release candidate posted to the PageSpeed Google Group last week that seems specifically targeted at v4. (Current version is 1.10, that RC is for 1.11.x) Might be better than hacking the compatibility value and hoping the UI changes don't blow anything up too badly.



Only top voted, non community-wiki answers of a minimum length are eligible