Now as you can see from above I’m using live_search_bkd.jpg as background for input field. Chrome render this field perfectly, but I have problem on ff. Firefox shows this input field with one line above background image.
how can I solve this ?
Hi, it’s hard to see what you’re seeing without the images.
However, your background shorthand syntax isn’t quite right - the order of the properties is
background-color background-image background-repeat background-attachment background-position
e.g.
background: transparent url(../_images/login_bt.jpg) no-repeat top left;
I’m going to go a bit offtopic and say the form also happens to be invalid and the label needs a “for” attribute to match the id of the text input. And the CSS is waaaay heavier than you need. You really don’t need #longidname#anotherlongidname#anotherelement .class {something} because it’ll make your code hard to read and harder for your to debug.
Tested locally, Chrome had the same problem on my machine, as did Opera.
Anyways, resetting the margins and padding for all our friends seems to line the “enter query” and background image on #live_search#livesearchform#inputString,#livesearch_form#livesearchform#ps up.
Tested locally in FF, Opera, Safari, Chrome, IE6, IE7 and IE8
Anyways, resetting the margins and padding for all our friends seems to line the “enter query” and background image on #live_search#livesearchform#inputString,#livesearch_form#livesearchform#ps up.
I am strongly against removing padding from everything using the * selector and especially when it comes to forms.
If there’s padding on the form itself, it’s safe enough to remove it, but not the submit for example.
Performance problems, even on a very large site would probably still not be very noticable.
The page in question would have to be humongous but then you’d have to ask yourself, is having a page that big really a good idea? If it’s a results page you could use pagination or if it’s just a regular page cut up the content into sections for the user to read. Studies have shown (don’t ask me to quote one because I can’t lol), I think, that longer pages tend to have users exit your site. THey want an answer and they don’t want to read all day to find it.
I fully agree buddy. It’s like those css compression discussions to save loading time. The milliseconds they save are for a user hardly noticeable (maybe if he’s on a medieval connection, it does lol).
And no, you’re not rambling about those studies. I’f i’m not mistaken it’s about 15 seconds a user spends searching for the relevant info. And the info has to be above the fold…
“It’s clear that CSS selectors with a key selector that matches many elements can noticeably slow down web pages. The key is focusing on CSS selectors with a wide-matching key selector. This becomes even more important for Web 2.0 applications where the number of DOM elements, CSS rules, and page reflows are even higher.”
I’m curious if anyone (zcorpan/paul) has set up test cases?
I don’t think that there are actual figures to back that statement up: the fact that they can slow down a page is a logical deduction but what is ‘noticeably’ ? 1 second, 30 seconds, 1 minute…? And is ‘noticeably’ meant for dial up users, broadband users…?
When we (=web page designers, - developers) usually say that something slows a page down, it’s because we use common sense but mostly it’s not backed up with figures
‘You should use sprites for your nav’ “Why?”
“Each one of those images is a separate HTTP-Request, and the more of those, the less efficient your page is.”
‘Makes sense but you have figures?’
“Erhm, no but you can do a google”
(the above is not invented but a discussion i had on a different list)
What i want to make clear is that our gut instinct tells us that it could slow down a page but not how much and if it’s worth trying some method involving more mark up or ‘high tec’ technique
8 seconds delay in IE6, FF, Chrome, Safari all way under 2 seconds. To bad the graph jumps from 0 to 2000 ms so i can’t do an accurate estimate on safari and chrome (less the 1 second???)
common sense: not always
figures: numbers
ms: subjective
Our good friends IE are a bit slow but i’m wondering if a user in the real world would notice the ‘big’ difference. For me, loading and reflow was not that heavy… but i guess that’s something subjective
I doubt they would notice…not everyone stares at their computer screen avidly while they wait for a page to load. They mess with other open tabs or other open programs.