cross-browser

I'm working on getting my site to support the eTag/If-None-Match browser cache, but I'm not sure which browsers do/don't support it. Can anyone point me to a list? I can't imagine it's universal, but I haven't found anything that supports that claim. cheers, Mike Steve If-None-Match was Specified in HTTP 1.1 (June 1999): http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol According to Wikipedia: By March 1996, pre-standard HTTP/1.1 was supported in Arena, Netscape 2.0, Netscape Navigator Gold 2.01, Mosaic 2.7, Lynx 2.5, and in

What should i keep for body , {font-size: 100.01%; } or { font-size: 100%; } ? what is {font-size: 100.01%; } ? and is it really good to mention font-size in html{} even If I'm using body {font-size: 62.5%;} Edit : 3 May 2010 Today i found info about 100.01% at here - http://www.communitymx.com/content/article.cfm?cid=FAF76&print=true This odd 100.01% value for the font size compensates for several browser bugs. First, setting a default body font size in percent (instead of em) eliminates an IE/Win problem with growing or shrinking fonts out of proportion if they are later set in ems in other

This is a duplicate from UI.StackExchange.com: https://ux.stackexchange.com/questions/1004/mixing-percent-and-fixed-css Should you ever apply percentage and fixed CSS together? Will it cause problems, and if so what kinds? Does mixing degrade browser render performance? Will mixing give you weird results on initial load with progressive rendering browsers? Below is just a dumbed-down example of mixed usage, it could be any mixture. I am not looking for validation of the example. I have heard you should never do what I have in the example below, so I am trying to find out if using CSS in this

I'm generating a page for an upcoming portal site, and I've got an HTML element with some optional content. I'd like the element to not render if it is empty, but adding some padding to it causes it to render. How do I add padding to the content, but only if content is present? .someElement{padding-top: 5px;} HTML in question: <div class="someElement">With padded content</div> <div class="someElement"><!-- shouldn't render since it has no content --></div> Basically, I'd like the second element, above, to not take up any space. I'm testing in all major browsers, using XHTML 1.1 doctype.

I recently asked a question that got shot down for being too strongly worded. I'm having another go today because it's something I really am concerned about and I really do want feedback and ideas from the smart people on SO. IE6 isn't quite the bane of my existence, but it's close. I'm a web-developer and spend too much time fixing things for IE6. Considering its age and relative quality, I'm shocked so many people are still using it. I understand that some companies still use it for legacy internal webapp support but I've found two companies now that haven't upgraded solely because XP's

jQuery 2.0 is increasingly mature: http://blog.jquery.com/2013/03/01/jquery-2-0-beta-2-released/ jQuery 2.0 breaks compatibility with older browsers, so one must know when to stay with jQuery 1.9. The recommended approach is to use IE's conditional comments: <!--[if lt IE 9]> <script src="jquery-1.9.1.js"></script> <![endif]--> <!--[if gte IE 9]><!--> <script src="jquery-2.0.0b2.js"></script> <!--<![endif]--> current web development best-practice suggests that we should be avoiding browser-sniffing or user agent string parsing, but isn't this sort of what conditional comments are? does jQuery

I have a web application that listens for Server Sent Events. While I was working and testing with multiple windows open, things were not working and I banged my head for several times looking in the wrong direction: eventually, I realized that the problem was concurrent connections. However I was testing a very limited number and even if I am running the test on Apache (I know, I should use node). I then, switched browser and noticed something really interesting: apparently Chrome limits Server Sent Events connections to 4-5, while Opera doesn't. Firefox, on the other hand, after 4-5