<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar/32074232?origin\x3dhttp://site-designer.blogspot.com', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe", messageHandlersFilter: gapi.iframes.CROSS_ORIGIN_IFRAMES_FILTER, messageHandlers: { 'blogger-ping': function() {} } }); } }); </script>

WebDesigner Paginas Web Designer
webDesigner Freelance Paginas Web

 
WebDesigner Site-About UsContact


August 21, 2006

Firefox Make CSS Work across all modern browsers

Here are the CSS styling features that are not well supported across browsers. This list is fairly rough, because CSS property support is a minefield of special cases:

  • Complex table styles, especially tabular values for display

  • Fancy border-style values, such as groove

  • Applying and then removing display : none

  • Expecting font-family values to display identically across browsers

  • Expecting list-style-type icons to display identically across browsers

  • outline styles

  • padding styles (see the "Box model" section later in this hack)

  • Properties in CSS2 that aren't in CSS2.1

  • Complex style rule selectors that depend on two or more identifiers

  • Mozilla-specific style selectors, properties, and values prefixed with -moz.

In addition to these specific properties worth avoiding, there are three issues that affect stylesheets, layout, scripting, or a combination of all three

1 Comments:

Post a Comment

<< Home