How To Create an IE-Only Stylesheet
If you read this blog, there is a 99% chance you've had a hair-pulling experience with IE. But if you are worth your salt as a CSS coder, you should be able to deal with it. I am of the opinion that you can handle anything IE can throw at you without the use of hacks. Hacks are dangerous, since they are based on non-standard exploits, you can't predict how they are going to behave in future browsers. The tool of choice for fighting IE problems is the conditional stylesheet. IE provides comment tags, supported all the way up to the current IE 8 to target specific versions, as well as greater-than/less-than stuff for targeting multiple versions at once.
Why use conditional stylesheets?
- You got problems, they need fixin'
- Keeps your code hack-free and valid
- Keeps your main stylesheet clean
- Perfectly acceptable technique, sanctioned by Microsoft
And remember, these conditional tags don't have to be used only for CSS. You could load JavaScript, or even use them down in the content of your site to display special IE-specific messages.
The Code
This would go in your <head> with all the other regular CSS <link>ed CSS files. The opening and closing tags should be familiar, that's just regular ol' HTML comments. Then between the brackets, "IF" and "IE" should be fairly obvious. The syntax to note is "!" stand for "not", so !IE means "not IE". gt means "greater than", gte means "greater than or equal", lt means "less than", lte means "less than or equal."
Target ALL VERSIONS of IE
<!--[if IE]> <link rel="stylesheet" type="text/css" href="all-ie-only.css" /> <![endif]-->Target everything EXCEPT IE
<!--[if !IE]><!--> <link rel="stylesheet" type="text/css" href="not-ie.css" /> <!--<![endif]-->Target IE 7 ONLY
<!--[if IE 7]> <link rel="stylesheet" type="text/css" href="ie7.css"> <![endif]-->Target IE 6 ONLY
<!--[if IE 6]> <link rel="stylesheet" type="text/css" href="ie6.css" /> <![endif]-->Target IE 5 ONLY
<!--[if IE 5]> <link rel="stylesheet" type="text/css" href="ie5.css" /> <![endif]-->Target IE 5.5 ONLY
<!--[if IE 5.5000]> <link rel="stylesheet" type="text/css" href="ie55.css" /> <![endif]-->Target IE 6 and LOWER
<!--[if lt IE 7]> <link rel="stylesheet" type="text/css" href="ie6-and-down.css" /> <![endif]--><!--[if lte IE 6]> <link rel="stylesheet" type="text/css" href="ie6-and-down.css" /> <![endif]-->Target IE 7 and LOWER
<!--[if lt IE 8]> <link rel="stylesheet" type="text/css" href="ie7-and-down.css" /> <![endif]--><!--[if lte IE 7]> <link rel="stylesheet" type="text/css" href="ie7-and-down.css" /> <![endif]-->Target IE 8 and LOWER
<!--[if lt IE 9]> <link rel="stylesheet" type="text/css" href="ie8-and-down.css" /> <![endif]--><!--[if lte IE 8]> <link rel="stylesheet" type="text/css" href="ie8-and-down.css" /> <![endif]-->Target IE 6 and HIGHER
<!--[if gt IE 5.5]> <link rel="stylesheet" type="text/css" href="ie6-and-up.css" /> <![endif]--><!--[if gte IE 6]> <link rel="stylesheet" type="text/css" href="ie6-and-up.css" /> <![endif]-->Target IE 7 and HIGHER
<!--[if gt IE 6]> <link rel="stylesheet" type="text/css" href="ie7-and-up.css" /> <![endif]--><!--[if gte IE 7]> <link rel="stylesheet" type="text/css" href="ie7-and-up.css" /> <![endif]-->Target IE 8 and HIGHER
<!--[if gt IE 7]> <link rel="stylesheet" type="text/css" href="ie8-and-up.css" /> <![endif]--><!--[if gte IE 8]> <link rel="stylesheet" type="text/css" href="ie8-and-up.css" /> <![endif]-->Universal IE 6 CSS
Dealing with IE 6 and below is always an extra-special challenge. These days people are dropping support for it right and left, including major businesses, major web apps, and even governments. There is a better solution than just letting the site go to hell, and that is to server IE 6 and below a special stripped-down stylesheet, and then serve IE 7 and above (and all other browsers) the regular CSS. This is been coined the universal IE 6 CSS.
<!--[if !IE 6]><!--> <link rel="stylesheet" type="text/css" media="screen, projection" href="REGULAR-STYLESHEET.css" /> <!--<![endif]--> <!--[if gte IE 7]> <link rel="stylesheet" type="text/css" media="screen, projection" href="REGULAR-STYLESHEET.css" /> <![endif]--> <!--[if lte IE 6]> <link rel="stylesheet" type="text/css" media="screen, projection" href="http://universal-ie6-css.googlecode.com/files/ie6.0.3.css" /> <![endif]-->Hacks
If you must...
IE-7 ONLY
* html #div { height: 300px; }NON IE-7 ONLY:
#div { _height: 300px; }Hide from IE 6 and LOWER:
#div { height/**/: 300px; }html > body #div { height: 300px; }Argument against conditional stylesheets
We shouldn't need them. They are against the spirit of web standards.
Argument for conditional stylesheets
Yeah, but we do need them
source url: http://css-tricks.com/how-to-create-an-ie-only-stylesheet/
The Ultimate Guide to Sales Force Automation: 100-Plus Links and Resources
If your company wants to do well in sales, it's important to have a system that helps it keep up with the pace of today's marketplace. SFA (Sales Force Automation) is a great way to do so, and it offers numerous options for eliminating or streamlining tasks that would otherwise distract your salespeople from doing what they do best: selling. Check out these resources to see how you can put this sort of system to work for you.
How to Avoid the Four Most Common Mistakes of Sales Process Mapping
January 8, 2009 by admin
Filed under Sales Process Mapping
By Michael J. Webb
Process mapping is a well-known technique for creating a common vision and shared language for improving business results. It helped one management training and development firm realize that people within their sales department had been working at cross purposes, and crucial executive-level discussions with customers were not taking place. Based on sales process mapping, the leaders reorganized their sales operations so that job descriptions and performance measures focused more on the customer. In six months, they reversed a five-year slump and earned big bonuses for team members. In another case, sales process mapping helped a large manufacturer’s national account teams discover a powerful new way to coordinate with field salespeople, yielding far more new business opportunities than expected.
Prospect Qualification Improvement Initiative
One possible area to focus on is the input specifications, also known in the sales world as qualification. For example, an electrical utility was attempting to sell a new array of technical services to its customers. They asked for help with closing skills because their close ratio was less than 10%. Sales people were overburdened, chasing as many deals as they could but not making their numbers. Prospects seemed to delay their decisions over and over. They went with engineering firms they already knew. Or deals simply died for no apparent reason.
Implementing a Formal Selling Process and Performance Measures in a Sales Organization
Joe Vavricka and Barry Trailer
Trailer Vavricka, Inc.
Summary: This paper describes implementing a process management framework and performance measurements into a corporate sales organization. It begins with describing the traditional approach to sales management and the potential impact of improving sales performance on revenue and profits. Then, the company s process-based approach to sales management is described along with the key performance measures most relevant for monitoring sales revenue production across sales, marketing, and customer support departments. This case illustrates that viewing sales as a production process and implementing process performance measures will enable a company to significantly increase sales and improve sales predictability by increasing productivity throughout the process.
Reconnect Sales Management to Profitability
by Jonathan Byrnes
How to Setup a Dedicated Web Server for Free
Dec 4th in News, PHP by Alex Villmann
All great websites have a great server behind them. In this tutorial, I'll show you how to set up a dedicated web server (with Apache, MySQL, and PHP) using that old computer you have lying around the house and some free software.
How to Create A Sales Pipeline
There are any number of sales pipeline stages you can use: I’m going to use Leads, 10% Opportunities, 50% Opportunities, 90% Opportunities and Closed Won/Lost. I first adopted this methodology when I began using Salesforce.com which mapped well to how my mind works.
Sales Opportunity Management
Opportunity management enables sales teams to work together to close deals faster by providing a single place for updating deal information, tracking opportunity milestones, and recording all opportunity-related interactions.
Sales Stages
Below is a sample checklist that could be used as a starting point for the development of a company’s sales process.
Prospect Stage:
- Prospect fits our target customer criteria
- Prospect's vision and key operating goals documented
- First contact made (phone, letter, email, or personal)
- Potential opportunity identified
- Initial meeting scheduled and confirmed