CSS Trouble in Safari? Check your comments
If you're having CSS display problems in the Apple Macintosh Safari browser, for an otherwise great-looking web site, your issue may be incorrect commenting etiquette.
/* Comment */
is cool.
// Comment
could cause issues.
The former is simply proper cascading style sheet comment markup, and the latter is wrong, but it seems other browsers are more forgiving than Safari. We had people saying how much they liked the site, how good it looked, and I kept testing it in Safari and getting into a really bad mood.
Then I found my incorrect comment code in one spot in the CSS file, and all was happiness again.
If you're having CSS display problems in the Apple Macintosh Safari browser, for an otherwise great-looking web site, your issue may be incorrect commenting etiquette.
/* Comment */
is cool.
// Comment
could cause issues.
The former is simply proper cascading style sheet comment markup, and the latter is wrong, but it seems other browsers are more forgiving than Safari. We had people saying how much they liked the site, how good it looked, and I kept testing it in Safari and getting into a really bad mood.
Then I found my incorrect comment code in one spot in the CSS file, and all was happiness again.
More like this
- Email and domain hosting on separate servers: MX Record Troubles and Solution
- A fatal error without any of your code in the backtrace: check your form_alter
- Checking out your contributed module from CVS to work on it more
- Views creating blank rows? Check your node type filtering
- Line length for comments to wrap, Drupal best practices


Comments
Post new comment