CSS Problem with Google Chrome and Safari?
Just remove the line-height: 40px you have in your #navMenu. However, you have a mess there of ul and li elements. There should be simplified to a single ul and a list of li elements.
Try replacing: With: Making that change with Chrome Inspector at least fixed the issue.
Thank you for your reply, but when I tried that change it broke the styling in IE and Firefox. – Jenny Jun 17 at 13:38.
The following CSS hack is based on a prior CSS fix called the Stokely Safari Hack, which affected all Safari (v1-3) browsers, including versions 1.2, 1.3, 2.0, 3.0(and even 4 now!). Our developers innovated this fix to address issues in the various browsers related to CSS and layout differences found among Internet Explorer, Safari for Mac, Chrome, and Firefox. (This hack was originally posted at www.stormdetector.com, one of our developer's websites).
The powerful thing about this hack is that it not only remains a powerful and reliable hack for fixing Safari Mac browser issues in your website style sheets, but also has some built in fixes for other browsers as well, like IE5, IE6, IE7, IE8 and older Mozilla Gecko browsers like older Firefox browsers or Netscape 6. It turns out, that this fix or hack also addresses newer IE7 AND IE8, and can be combined with the popular Star Hack for Internet Explorer 5 and 6, to control styles, not only in IE 5 and 6, as well as Safari, but isolate IE 7 and 8 styles as well. What this means, is that the GiantIsland CSS Hack can control styles in 6 different browsers and versions using one style fix!
So, if you still have a bug that plagues the IE7, IE6 or IE5 series browsers as a group, as well as Macintosh Safari and Google Chrome browser, we have developed a new style sheet hack for you that will not only allow you to target IE 5 and 6, but also 7 and 8, as well as Safari as needed in your CSS style sheets. If you need to trigger a rule for IE 7 and not 6, this will do it! Or if you need to affect IE6 but not IE7, IE8, or IE5, this will do it!
If you need to fix Safari/Chrome from all Internet Explorer and Firefox agents, this will also work for you! Because Webkit is the engine behind Safari and Chrome, they seem to share much of the same rendering issues, that separate them from FF and IE. So, its up to you to use the code creatively in your sites!
The hack is based on the inability for all the major browsers to interpret attribute selectors ("") correctly in CSS. Placing or rather misplacing these is what creates the hack and allows us to control which browsers see which rules in the CSS hack. To use the hack, first create a single style which uses misplaced attribute selector as shown below.
Wrap a series of "Mac IE only hidden" comments characters around this rule to protect it from old IE5 for Macintosh, to be safe.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
Strange problem with Google Maps and Ajax in Google Chrome and Safari?
Problem with my css which is working on mozilla firefox but not on Chrome and safari?
JQuery SESSION problem with Google Chrome and Safari on MAC OS x 10.5 only?
OPEN DISCUSSION: Flock 3 has been released it is based on google chrome Would you ever use a google chrome based flock for social networking?
Chrome and Safari add 'border line' to img with css fixed height and width?
Does it annoy you when someone uses the google bar to google google and then uses google to google...?