I'm changing over a site from HTML to Wordpress (for the first time, so be gentle!) and I ran into an issue with Google Chrome applying styles that I've never knew existed! In this case I'm referencing the style that positions the bg.gif image background. In both IE9 and Firefox the background elements seem to work just fine, but in Google Chrome I'm having the issue.
If you go to this site: http://www.richmindonline.com/doggy2/ then right-click the upper right corner of the page in Google Chrome, then click "Inspect Element", you will notice styles that are being applied that have nothing to do with my stylesheets.
Could someone provide some guidance as to how to fix this. I've already tried adding my own styles to trump the Chrome styles, but it's not working.
Which styles are you trying to override? What you're seeing are browser defaults - all browsers have them whether they show you or not.
What I'm seeing in the inspector is Chrome identifying the text direction and locale. Are you using a CSS reset?
http://www.cssreset.com/
Should go a long way in starting all browsers at the same default.
Related
This is really odd. I'm not complaining that something works, but it is very surprising ..
On my website I had the usual css :hover for the navigation to reveal sublinks. But on the mobile browsers this needed some js help to make it work (as you can see from those many posts about "css hover not working on mobile browsers")
I made a simple script to fix the hover problem. But today as I was rewriting the code, since I noticed that it was not fully working as intended, I removed the entire mobileDetect.js which was handling the mobile hover. And now it works, without any additional scripts.
I tested it with chrome and safari on my ipad and iphone. It works as intended... did I misse out a big mobile browser update or something?
I use Jquery from google, no framework and standard HTML5.
Here is the site : (easy-sailing.ch) "EVENTS" and "AUSBILDUNG" are the mentioned navigations with sublinks.
I am just wondering if this is some odd anomaly and therefor should put my script back in or just enjoy the good news? :S
as far as i remember it has always been working...
...it is just not needed because there's no cursor and hover happens usually when you click (touch in this case) and you'll leave the page before noticing hover.
on android i can observe it when i touch+slide up or down.
I have fixed this for me by removing :hover selectors/rules at runtime https://github.com/kof/remove-hover
Background story: I have a page with multiple CSS that override each other. There are so many crossed out CSS style, so I don't want to see them.
I know Firebug on Firefox provide this feature (Only Show Applied CSS), which can show what CSS style in what CSS file is being applied (neat !).
How do we have this feature on Chrome ? I tried install Firebug Lite for Chrome but no luck.
PS: Chrome have Computed Style tab, but it does not show what style come from what CSS file.
In the Chrome dev tools, in the right hand column (where CSS is shown in the Elements panel), the first section is called "Computed Style". If you deselect "show inherited", you get a neat list of the styles that actually apply to the element. Does that help?
I built and tested my site in Firefox but now when wanting to launch I realized that there is extra padding showing up between the menu and posts as well as borders on some of the images when viewed in IE9.
I have looked through all of the CSS and can't figure out what might be causing either of these problems. Any ideas would be great.
Here is the site: http://beautyintheweeds.com
Thanks!
Every browser has different default css rules. Use a css reset to bring everything to the same defaults.
Is there a way to move the checkboxes that disable CSS styles in the WebKit Inspector that is baked into Safari and Google Chrome from the far right over to the left, next to the declaration how Firefox's Firebug does it? To disable styles, one must go over to the far right, which can be hard to eye trace when the style declaration list is very long. On top of that, sometimes the new Lion style scrollbars can get accidentally clicked. I hear that even the Web Inspector in WebKit is laid out via CSS, so this should be relatively easy. Any help? Even if someone could get me to the style sheet for the WebKit inspector I could figure out the CSS. Thanks in advance!
Here's some screenshots to demonstrate what I mean:
WebKit CSS Inspector
Firebug CSS Inspector
(Couldn't post images with Stack Overflow's setup as I'm a new account)
There's a webkit inspector stylesheet located at github: https://gist.github.com/1153881
I'm trying to learn CSS. I've taken great pains to get everything right. My pages all validate and they look correct on Firefox and mostly correct on Chrome. However IE is all over the place. In relation to Firefox, the following is wrong in IE (in order of importance):
the main body box is pushed below where the left boxes end
the upper-right drop-down stuff (mouse over "Settings") is totally off in the weeds (it's off in Chrome also but in a different way)
"Recipes" tab is supposed to have no visible bottom border
search button is askew in relation to search box
logged out version: the upper-right login elements are askew
Logged in,
Logged out,
CSS,
Links, functionality, etc. are not guaranteed to work on these pages. It's just static snapshots to show layout.
Can anyone point me in the right direction for whatever I'm doing wrong?
You need to Reset your CSS (Dean, above recommends Eric Meyer's Reset CSS). I prefer Yui Reset CSS (I actually like their own Reset / Fonts / Grids CSS). As part of doing this you also need to use Standards Mode.
Finally, you need to be aware that some things will differ in browsers no matter what. So if you run into this situation, it's either work around it, or live with it.
What version of IE are you running? Sounds like most of your issues may be caused by the IE Box Model Bug.
I never start a new website design in css without putting Eric Meyer's Reset CSS in first.
It resets all the differences in all the browsers, so that you've got a even playing field to start from.
From there-out, everything should be the same in all browsers.