Skip to main content
added 325 characters in body
Source Link

You should show your message styled as an error message, not an information message, because there was a problem.

An error message merely containing information doesn't mean it should be styled as an information message, because errors should always contain information. An error which contains no information, like the following...

Error: error: There was an error caused by: error

... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. Naturally, they ought to be provided with useful information about what went wrong and what they can do about it (insofaras they'll care).

Define cases for where to use your Information style

You should probably work out a well-defined casestandard for when the information style should be used. It's obvious enough for error, sowarning, and success messages, but it's particularly important to work this out for a class of message such as "information" because of how vague that you can recognise exactly when it should be usedname is. The case should not simply be "this message has information in it", since all

Consider for a moment that all messages acrossin your website will probably be information, but you wouldn't want to mark all of those with an information icon. 

An information style might actually not be useful: for instance, the blue styling on one of my local government's websites is actually a direction style instead, and is used in the case where someone is being informed about related, but tangential, information or services. All other messages providing them with information are just plain text.

You should show your message styled as an error message, not an information message, because there was a problem.

An error message merely containing information doesn't mean it should be styled as an information message, because errors should always contain information. An error which contains no information, like the following...

Error: error: There was an error caused by: error

... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. Naturally, they ought to be provided with useful information about what went wrong and what they can do about it (insofaras they'll care).

You should probably work out a well-defined case for when the information style should be used, so that you can recognise exactly when it should be used. The case should not simply be "this message has information in it", since all messages across your website will be. An information style might actually not be useful: for instance, the blue styling on one of my local government's websites is actually a direction style, and is used in the case where someone is being informed about related, but tangential, information or services.

You should show your message styled as an error message, not an information message, because there was a problem.

An error message merely containing information doesn't mean it should be styled as an information message, because errors should always contain information. An error which contains no information, like the following...

Error: error: There was an error caused by: error

... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. Naturally, they ought to be provided with useful information about what went wrong and what they can do about it (insofaras they'll care).

Define cases for where to use your Information style

You should probably work out a well-defined standard for when the information style should be used. It's obvious enough for error, warning, and success messages, but it's particularly important to work this out for a class of message such as "information" because of how vague that name is.

Consider for a moment that all messages in your website will probably be information, but you wouldn't want to mark all of those with an information icon. 

An information style might actually not be useful: for instance, the blue styling on one of my local government's websites is actually a direction style instead, and is used in the case where someone is being informed about related, but tangential, information or services. All other messages providing them with information are just plain text.

expanded & corrected vocabulary
Source Link

You should show your message styled as an error message, not just an information message, because there was a problem.

An error message merely containing information doesn't mean it should be styled as an Informationinformation message, because errors should always contain information. An error which contains no information, like the following...

Error: error: There was an error caused by: error

... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. You shouldNaturally, they ought to be providing themprovided with useful information about what went wrong and what they can do about it, to whatever degree of information (insofaras they'll understand, care about).

You should probably work out a well-defined case for when the information style should be used, andso that you can recognise exactly when it should be able to actused. The case should not simply be "this message has information in it", since all messages across your website will be. An information style might actually not be useful: for instance, the blue styling on one of my local government's websites is actually a direction style, and is used in the case where someone is being informed about related, but tangential, information or services.

You should show an error message, not just an information message, because there was a problem.

An error containing information doesn't mean it should be an Information message, because errors should always contain information. An error which contains no information, like the following...

Error: error: There was an error caused by: error

... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. You should be providing them with information about what went wrong and what they can do about it, to whatever degree of information they'll understand, care about, and be able to act on.

You should show your message styled as an error message, not an information message, because there was a problem.

An error message merely containing information doesn't mean it should be styled as an information message, because errors should always contain information. An error which contains no information, like the following...

Error: error: There was an error caused by: error

... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. Naturally, they ought to be provided with useful information about what went wrong and what they can do about it (insofaras they'll care).

You should probably work out a well-defined case for when the information style should be used, so that you can recognise exactly when it should be used. The case should not simply be "this message has information in it", since all messages across your website will be. An information style might actually not be useful: for instance, the blue styling on one of my local government's websites is actually a direction style, and is used in the case where someone is being informed about related, but tangential, information or services.

Source Link

You should show an error message, not just an information message, because there was a problem.

An error containing information doesn't mean it should be an Information message, because errors should always contain information. An error which contains no information, like the following...

Error: error: There was an error caused by: error

... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. You should be providing them with information about what went wrong and what they can do about it, to whatever degree of information they'll understand, care about, and be able to act on.