I'm in the process of redesigning a website for a friend from school. Along the way I've encountered a weird bug in Google Chrome: I've styled the contact form (very basic, an input each for name and email address and a textarea for comments) using a CSS3 gradient background.
Everything works fine – until you click inside a field to enter data, whereupon the name input and textarea take on the background colour of their parent form element. The email input, meanwhile, retains the gradient both when focussed and when not (as desired).
Please visit http://www.chrisphilpot.co.uk/lucycooper2012/ to see what I am getting at. As I say, it seems to look fine in Firefox and IE9 picks up on the flat background #FFF which will do for the time being!
Do you have any bright ideas to fix this? I've relinked the page to the full, uncompressed CSS so feel free to have a rummage. The main styles for the form are in: http://www.chrisphilpot.co.uk/lucycooper2012/css/form.css
Thank you for your help and time!
Related
This is one problem I can't understand. I'm using windows 10 and by default the form border should be displayed like this:
But for some reason or the other, my windows form app's form border is like this:
... despite the form border property is set to FixedSingle. I also tried the same with form border property Fixed3D but still it is of no use.
It would be great if someone could guide me about how this can be fixed and the reason my form's border is wired. Please download the images to get a clarity of what I'm asking.
NOTE
Fixed here means to get back the default form border.
I also use Bunifu Framework. However I don't know the relevance it has here
The image attached was taken during debugging
I'm having an issue with getting Googlebot to correctly render my webpage(s).
It's rendering the header and one "row" of my page (just the page's top background picture), and then failing to render anything beyond that, not even the footer, missing about 3/4 of the page.
My site is www.runparis.fr and screenshots of the rendered fetch are attached.
Other potentially relevant information includes:
The code that was fetched is missing nothing
The fetch status is complete (no missing resources)
The problem is site-wide; it happens on all my pages
When I check the cache the whole page is rendered perfectly
Fetch as Google (mobile) renders the site perfectly
The site looks fine in any of my browsers
There's nothing funky going on in my page; It's just background images and text. Easy stuff.
My questions are:
Will google's inability to render the page have an impact on how Google ranks it?
Is there any advice for solving the problem and having google render the page correctly?
Thanks for any help or advice anyone can offer!
Googlebot render 2
Edit:
I've done another Fetch as Google and render for a test page and found that Googlebot will stop rendering after it has rendered any background images that I've set to "full height" in my page builder in my Wordpress installation; that is, any image that is set to take up the full height of the browser window kills the render.
So, it will render everything until it hits this image, renders that, and then stops.
As stated before, my page isn't fancy; It's just simple background images and text. It surprises me that Googlebot has trouble rendering what any browser can render perfectly, especially given the simplicity of the pages!!
So, my questions are:
Will Google not being able to render my page impact the way Google ranks my site? (given that what's in the cache renders fine on my browser)
And, Is this a common problem? Are there any fixes that will let Google render my pages correctly?
Some new information supplied by an external source:
"validator.w3.org/nu/?doc=http%3A%2F%2Frunparis.fr%2F"
"jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Frunparis.fr%2F&profile=css3&usermedium=all&warning=1&vextwarning=&lang=en"
The various errors and warnings might explain why rendering is hampered in some tools such as Google Fetch and render.
Browsers are much more forgiving than all these validation and rendering tools.
I'm guessing that in Google's rendering tool the css rules that set the background image(s) and foreground image(s) and text content are being applied in the wrong order so background stuff ends up on top of foreground.
Does this new information help anyone understand why Googlebot would be having trouble to render the page?
I have experienced the same problem, the only viewable thing on the renderer was the hero section, and it was caused with defining height:100vh; for the hero section.This problem occur when using vh css units, or in some cases height:100%;
Here is the thread and discussion that really helped me out to understand the issue:
I believe that the google bot is doing this:
1. Looking at your website with a 1024x768 viewport.
2. Checks how tall the window.scrollHeight is
3. Resizes it's virtual browser to be the same height as the window.scrollHeight
4. Takes a screenshot and
5. Checks to see what elements are visible, and tallies SE score as appropriate. (Dinging content that is not visible.)
I partially solved this issue with inserting extra rules into mediaqueries: So for resolutions around 1024px width, I put max-height:800px; (rule height:100vh; stayed active) on my hero section, and on mediaquery for rules around 1280px width and up, I set max-height:none; (rule height:100vh; is active).
I'm still loosing around 30px of height in the renderer, but that's being cut off at the end of the page, with no text and any meaningfull content.
I have the similar issue with (Google Mobile-Friendly) tool and (Fetch as Google) mobile version is broken because Googlebot is not loading my style.css and affect my rankings
so I output my stlye.css code for mobile manually
add_action('wp_head','load_mobile_styles');
function load_mobile_styles () {
if( wp_is_mobile() )
{
ob_start(); ?>
<style>
enter code here
</style>
<style>
enter code here
</style>
<?php
echo ob_ob_get_clean();
}
}
I have this template I'm working on and it's resizeable from full screen to the width of an iphone. My contact form field is fine at full screen, but when I resize my browser, it seperates really bad and not sure how to fix this to keep the fields right under each other. I have a before/after here:
http://www.webauthorsgroup.com/before.jpg
http://www.webauthorsgroup.com/after.jpg
I need to build a tab looking like this one:
https://www.facebook.com/auto.co.il/app_134594493332806
I know how to add an image and a comment box and i know of several "plain" ways to hide the content from non-fans, but i came across the above tab and i really like the way it shows thee content yet you cant engage it until you press the like button.
Any help please?
Thanks in advance.
Oren
Your link didn't work for me, but you can place a absolutely positioned div with a high z-index above the rest of your content to prevent the user from clicking on anything.
Update: Now that the link has been updated I see that they are doing exactly what I described above. In chrome if you right-click the background and select "inspect element" you will see the following computed style for the div:
rgba(0,0,0,0.796);
display:block;
height:1612px;
width:810px;
The content is blacked out simply with a div with a black background and some opacity. Just for fun, you can overcome their like gate (without liking) via chrome's JS console by selecting the iframe context and then entering the following:
$('.like_float_c').detach();
... now call youself a 'hacker' ;)
I'm working on a website template and Internet Explorer is giving me a headache since I'm unable to display the search form field and button correctly. z-index in CSS is not doing much either.
By the way, how can I move the input area after the loupe icon?
Check the website here:
http://gabrielmeono.com/yonature/
Chrome:
In IE8:
Three things:
IE8 does not support border-radius, which is being applied to that field.
Your CSS references a file that's missing, border-radius.htc which is for adding rounded corners in "all major browsers other than IE."
You should be able to add a left padding value on the field to force the text further to the right. It may be safer to make a white, rounded container and position the search button and text field within it.
Edit: I was wrong; the border-radius (curved-corner) file should work for IE6-8.